News for hackers. Stuff that matters.
Re:Fucking Shell Scripts by jamiesonbecker on Friday March 14, 2014 @10:49PM (#7403264)
Simple is almost always Correct.

Conversely, complex is almost always incorrect.

Re:Fucking Shell Scripts by mercurial on Saturday March 15, 2014 @03:58AM (#7403993)
"Simple enough is almost always correct". "Too simple for the problem domain" is almost always a synonym for "build a heap of absolutely terrible and verbose pile of complexity on top of the 'simple' system". See also sysvinit.
Re:Fucking Shell Scripts by kelnos on Saturday March 15, 2014 @04:10AM (#7404006)
Strongly disagree. Often complexity in your implementation is necessary to present a simple interface to your user.
Re:Fucking Shell Scripts by eikenberry on Saturday March 15, 2014 @05:43AM (#7404157)
The primary user of your implementation is the next developer to maintain it.
Re:Fucking Shell Scripts by kelnos on Saturday March 15, 2014 @06:37AM (#7404228)
The user of a piece of software is more important than its current or future maintainers.
Re:Fucking Shell Scripts by rschmitty on Saturday March 15, 2014 @08:36AM (#7404441)
Yes but current or future users want reliability, features, and speed. If you care about your users in the long term you should care about the project's maintainers.
Re:Fucking Shell Scripts by kelnos on Wednesday March 26, 2014 @06:07AM (#7472468)
I suggested a relative ordering of importance; nowhere did I imply that one was important and the other was not.
Re:Fucking Shell Scripts by eikenberry on Saturday March 15, 2014 @01:59PM (#7405435)
Thinking like this is why we have so much crappy software out there.
Re:Fucking Shell Scripts by bitwize on Saturday March 15, 2014 @03:15PM (#7405852)
To quote Ryan Dahl: The only thing that matters in software is the experience of the user.

How many more times must it be said? How many more times must Apple win -- and win big -- before open source nerds get the message?