6 ms·
"To be honest, looking back on it, Unix today is worse than the systems that Unix itself was created to get away from."
by justin66 12y ago
"To be honest, looking back on it, Unix today is worse than the systems that Unix itself was created to get away from."
- myg204 12y agoThat quote stood out for me as well. Great talk though, one of the best I've seen going over all the window manager issues he worked on over the years.
- fsck--off 12y agoHe said similar negative things about Unix in a 2004 interview with Slashdot. "I didn't use Unix at all, really, from about 1990 until 2002, when I joined Google. (I worked entirely on Plan 9, which I still believe does a pretty good job of solving those fundamental problems.) I was surprised when I came back to Unix how many of even the little things that were annoying in 1990 continue to annoy today. In 1975, when the argument vector had to live in a 512-byte-block, the 6th Edition system would often complain, 'arg list too long'. But today, when machines have gigabytes of memory, I still see that silly message far too often. The argument list is now limited somewhere north of 100K on the Linux machines I use at work, but come on people, dynamic memory allocation is a done deal! "I started keeping a list of these annoyances but it got too long and depressing so I just learned to live with them again. We really are using a 1970s era operating system well past its sell-by date. We get a lot done, and we have fun, but let's face it, the fundamental design of Unix is older than many of the readers of Slashdot, while lots of different, great ideas about computing and networks have been developed in the last 30 years. Using Unix is the computing equivalent of listening only to music by David Cassidy." http://slashdot.org/story/04/10/18/1153211/rob-pike-responds?nobeta=1 http://slashdot.org/story/04/10/18/1153211/rob-pike-responds...
- vidarh 12y ago> The argument list is now limited somewhere north of 100K on the Linux machines I use at work, but come on people, dynamic memory allocation is a done deal! This is a shitty argument. Dynamic memory allocation is a done deal, but it's trivial to bring down a system that doesn't limit it, and so you still need a limit beyond which users will still get errors. And usually, if you keep getting it, it's down to bad habits (globbing instead of find + xarg, the latter which lets you take full advantage of multiple processors)
- sp332 12y agoFind + xargs needs a lot more syntactic sugar before people start using it on a regular basis.
- Dewie 12y agoCan anyone here corroborate that there are better alternatives to operating systems than the Unix-likes? Maybe anyone that agrees with Rob Pike's view on this in particular? All I seem to hear is that Unix-y OSs are great, but I don't hear much about any potential alternatives. So I'm curious about them.
- wolfgke 12y agoWhat Rob Pike is refering to is of course Plan 9 and its derivatives (say Inferno). Whether you want to consider them Unix-likes or not is your choice (many HNers will say it's more Unix than Unix). If you look for desktop alternatives to Unix, OSes to look at are BeOS (an open source clone is developed under the name HaikuOS) and the Windows NT kernel (don't hurt me: the Windows NT kernel is IMHO far more elegant than, say Linux or Mach. What is crappy is especially the WinAPI; please look deep below the surface: Here Windows gets nice). The reason why you won't find many desktop/server alternatives to Unix can be read here: http://herpolhode.com/rob/utah2000.pdf http://herpolhode.com/rob/utah2000.pdf Thus lots of OS reserach is either focused on embedded stuff or virtualization instead of desktop or server. Accepting this, especially have a look at the L4 kernel family (a family of very small and fast microkernels). If you like highly secure designs, you'll probably like seL4, the first formally verfied kernel. Also QNX is worth a look (QNX is Unix, accepted; nevertheless a very elegant kernel design).
- pjmlp 12y agoWhile I agree with you regarding Windows. In respect to the WinAPI, OS/2 API shares part of the pain. And Xlib is way worse. I am looking forward to WinRT fixing some of the WinAPI issues.
- DanBC 12y agoBeOS http://en.m.wikipedia.org/wiki/BeOS http://en.m.wikipedia.org/wiki/BeOS Haiku https://www.haiku-os.org/ https://www.haiku-os.org/ Haiku http://en.m.wikipedia.org/wiki/Haiku_(operating_system) http://en.m.wikipedia.org/wiki/Haiku_(operating_system) Windows NT Kernel http://en.m.wikipedia.org/wiki/Architecture_of_Windows_NT http://en.m.wikipedia.org/wiki/Architecture_of_Windows_NT Windows NT Kernel http://blog.zorinaq.com/?e=74 http://blog.zorinaq.com/?e=74 (which references back to HN) L4 microkernels http://en.m.wikipedia.org/wiki/L4_microkernel_family http://en.m.wikipedia.org/wiki/L4_microkernel_family SEL4 http://sel4.systems/ http://sel4.systems/
- dobbsbob 12y agoPike also said: https://news.ycombinator.com/item?id=3075550 https://news.ycombinator.com/item?id=3075550 "..the Unix/POSIX/Linux systems of today are messier, clumsier, and more complex than the systems the original Unix was designed to replace. It started to go wrong when the BSD signal stuff went in (I complained at the time), then symlinks, sockets, X11 windowing, and so on, none of which were added with proper appreciation of the Unix model and its simplifications."
- _pmf_ 12y ago> "To be honest, looking back on it, Unix today is worse than the systems that Unix itself was created to get away from." That's my feeling about Go and C.