James Hague: "But all the little bits of complexity, all those cases where indecision caused one option that probably wasn't even needed in the first place to be replaced by two options, all those bad choices that were never remedied for fear of someone somewhere having to change a line of code... They slowly accreted until it all got out of control, and we got comfortable with systems that were impossible to understand."
Counterpoint by John Cook: "Some of the growth in complexity is understandable. It's a lot easier to maintain an orthogonal design when your software isn't being used. Software that gets used becomes less orthogonal and develops diagonal shortcuts." If there's ever been a system in
dire need of a complete redesign, it's UNIX and its derivatives. A mess doesn't even begin to describe it (for those already frantically reaching for the comment button, note that this applies to other systems as well).
Member since:
2005-11-13
No, not really. Sometimes, to access a file in the same directory I'm in, I have to do './filename' (or is it /.filename? I can't remember). Some of the most important files in the system are in a directory named etc. Do you know what 'etc' means?
http://en.wikipedia.org/wiki/Et_cetera
Why the f**k would you put a lot of critical files in a directory that means 'and other stuff' ?
The default text editor for crontab on the systems I have to use is still vi, which is one of the most user-UNfriendly pieces of shit ever written. Hard drives are named 'hda' in the file system. And I could go on and on.
I suppose many Unix gurus would argue that the pain of learning such an ass-backwards an incomprehensible system such as Unix is a rite of passage for enjoying its power. And I also understand that a lot of its eccentricities can be understood if you ever learn what a developer was thinking back in 1970-ish when all of this was being put together. I'm just saying that in 2012, we should be able to do better than this.