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:
2011-08-13
Assigning "/" to the hardrrive the OS is installed in and make everything else appear as a subfolder is silly
Wow, you really don't understand the Unix filesystem. The drive mounted as / is specified in /etc/fstab, and the physical drive files are located in /dev/. Some people mount /usr separately, some mount /var separately, and a lot of people using *nix at home mount /home separately. The beauty of the Unix filesystem is that nobody freaking cares what your partition scheme is unless you're running out of room. Mounting remote filesystems is completely transparent once they're mounted. Even NT does this internally; it only keeps drive letters as links because people are retarded and incapable of change.