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 519587
To read all comments associated with this story, please click here.
ricegf
Member since:
2007-04-25

OK,you've convinced me - you really have tried to avoid Unix all these years, haven't you? ;-)

You don't need a preceding ./ to access a local file; the filename does nicely. On ALL modern operating systems of significance, including Windows, "." refers to the current working directory (a most useful concept they borrowed from Unix). So if you have a file in the current directory named foo, you could access it as ./foo on Linux, .\foo on Windows, or simply foo on either one.

Windows tosses all of its files into C:\System, but then, it's a single user, local operating system. Unix and Linux are multi-user network operating systems - they segregate files into several different directories depending on purpose. /etc holds all configuration files not necessary for boot and basic system configuration. Since booting and configuring the system are unique concerns relative to normal operation, it's natural to think of all of the non-unique config data as "et cetera". But you're free to think otherwise.

When you launch vim in a modern version of Linux, you get an editing window. Those little icons at the top are buttons for the typical editing features that you would find in (say) Windows Notepad - from left to right on this computer, they are Open File, Save Current File, Save All Files, Print (separator), Undo, Redo (separator), Cut, Copy, Paste (separator), Find/Replace, Find Next, Find Previous (separator), Choose Session, Save Session, Run Script (separator), Make, Build Tags, Jump to Tags (separator), and Help. This doesn't strike me as more difficult - or indeed, much different - than Notepad (ignoring script and make support, of course - but surely you can just ignore those?).

Now, if you want to run vim within a text window, it's a bit more complicated - but ed in Windows isn't exactly a paragon of user friendliness, either! :-D

All of this is rather academic, though, since vim is not the default editor in a modern Gnome-based Linux system - gedit is.

But look, I really don't care if you want to hate Unix based on a comparison of whatever you use today compared to what you tried decades ago. Feel free. But doesn't that seem a little unfair? Just a thought.

Reply Parent Score: 6