Complexity is the death of usability. There comes a point in design when you must ask: `does the task at hand justify this complexity', `is this level of complexity necessary for the goal of this design'. Complexity is a necessity, not a desirable feat; and the complexity of a solution should always scale linearly with the complexity of the problem.
The task of design and implementation is not to find a solution to the problem; the task is to find the most simple (efficient) solution.
Simplicity and efficiency are not the same, but often go hand in hand.
For example, if a server owner has to set up and configure 4 different daemons for a task that could be completed by 1, the system is not only needlessly complex and difficult to configure, but inefficient due to constant inter-process piping of information and sharing of resources between daemons, as well as static libraries that may be loaded more times than is needed and such. In contrast, the creation of many small programs for a task that could be completed by 1 is not necessarily over-complex, but is still inefficient because the overhead of a process call actually can be significant. (Even in 2018, these things can stack up. 10 process calls may be fine, but 10000? 100000? You will begin to notice the problem of scaleability eventually.)
Complexity of configuration is often overlooked with `oh well you should know more about the system then, it's your own fault things went wrong' but I disagree. Increasing complexity of configuration makes errors more prone, errors that are often silent or hard to detect, errors that can manifest in security holes that are easy to overlook because of the sheer volume of configuration required. Does this socket have the correct permissions? Is this file readable is this one writable? Is this port in use by another server? Is this daemon loaded correctly? Alone these may seem easy to keep track of but can get overwhelming when having to configure many daemons together.
Complexity is the death of usability...
AAAAAAAAAAAAAAAAAAAAAAAAA I ruined the fucking gif
wat
I tried to make a good thread and fucked up
I guess gifs are too complicated for your usability lol
What a bad thread, can't even edit gifs properly
webm is the superior format anyways
I'm still getting used to windows xp give me a break
Did Ashley just die
Bites the dust only affects those who look into the eyes of the one that carries it
you could say she
[spoiler][spoiler]bit the dust[/spoiler][/spoiler]
yay ashley won't die
yes but that means you died
That's not funny
but how
“This bomb appears as a miniaturized form of Killer Queen that hides inside whoever it is planted in; it acts independently of Kira's will, manifesting only when the bomb is triggered. When planted in Hayato, it activates when Kira's identity is revealed audibly or through writing, as well as when other Stand users see the miniature Killer Queen. When this happens, a miniature Killer Queen enters the eye of the person and causes an explosion, killing them. The bomb can detonate multiple people simultaneously.”
Oh this is Jojo
yes
squish it
Did you write that?
Either way, I like it.
more accurate
Cruel
No but it's a copypasta now spam it
why did you do that
OHHHHHHHHH
did you finally get the joke
Yes did I do good
congrats now start reading part 8
of what
Jojo?
yes, or if you haven’t read the previous parts do that first
I don't know where to get it