Linked by Thom Holwerda on Fri 25th May 2012 14:55 UTC
General Unix 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).
Permalink for comment 519600
To read all comments associated with this story, please click here.
RE: Re:
by Soulbender on Sun 27th May 2012 07:36 UTC in reply to "Re:"
Soulbender
Member since:
2005-08-18

The commands have no logical consistency, for example ls prints the result by default, find doesn't,


find prints by default.

Someome needs to build wrappers for Unix's CLI commands, now.


More wrappers, awesome idea...

If this can't be fixed, let's at least fix it at terminal/GUI level so we can have HDD2:something.jpg


Because that's a great improvement. or not.

Using the space as both a seperator and a legit filename character is bad.


Are there any modern operating systems that doesn't do this? Nope, they all use space both as a command separator and a valid file name character.

I'm pretty happy you don't have any real input on how the OS should work.

Reply Parent Score: 4