3 ms·
Overall, I agree with Pike in 2000 and this article today. Systems software research has become stagnant and significantly derivative. The point isn't that a ne
by mcguire 12y ago
Overall, I agree with Pike in 2000 and this article today. Systems software research has become stagnant and significantly derivative. The point isn't that a new OS would come along and sweep everything away, the point is that nobody seems to be developing new OSs at all. Sort-of.
In 2000 or so, systems research had turned almost entirely into server performance measurement and tweaks. That trend seems to have changed, but things like Xen and VMware are not really new. IBM invented virtualization back in the middle ages; most of the more interesting things going on recently have involved using the idea. Likewise, moving stuff from Plan 9, etc., into Linux is cool (very, very cool), but it's not new, groundbreaking research.
That being said, there are a lot of nitpicks one can make with this article and with Pike's original talk.
The processor speed comparison in the table is not terribly valid, in my opinion. The more important number is front-side bus speed, which has not changed anywhere near as much. (Front-side bus speed dominates most of computing loads I see, and a great whopping chunk of the work in those areas where it doesn't dominate, video games and data-heavy computing, is in preventing the front-side bus from being the bottleneck.)
Pike was wrong about the language environment in 2000 and the table is wrong today. Heck, he might have been wrong about 1990. Programming language research in general and its specific applicability to systems (Hi, ATS!) has hotted up a lot since the '80s and '90s.
Pike's comment, "There has been much talk about component architectures but only one true success: Unix pipes. It should be possible to build interactive and distributed applications from piece parts," bothers me a lot. A great deal of component research has been a dead-end in general (See that pile of crap with CORBA and SOAP laying on top?) Further, I believe Pike never really understood distributed systems. I have seen Pike complain that Nagel's algorithm has no place in TCP/IP (although I haven't been able to find the reference in years), but if you want a more recent example, see Go---everybody likes CSP, right? Everyone except someone who has tried to implement a synchronous rendezvous on a network.
Finally, Plan 9 didn't fail. But it also didn't have any chance to succeed, if by success you mean taking over the world. It was a great research project, but I'd believe making someone who didn't grow up at Bell Labs should be against the Geneva Convention. (Anyone know when Plan 9 started supporting color?) Plan 9 is my prima facie evidence that Not Invented Here syndrome was invented at Bell Labs.
- bcantrill 12y agoThere's a lot that's wrong in here, but one thing that absolutely needs to be called out: ...things like Xen and VMware are not really new. IBM invented virtualization back in the middle ages Actually and in fact, what VMware did was new -- to the point that prior to this work, many reasonable people believed that x86 couldn't be virtualized without unacceptable performance penalty. Please read Keith and Ole's excellent ASPLOS paper[1] for an in-depth discussion of the novelty -- and the citation for this technology when it won the ACM Software Systems Award[2]. If you insist that VMware's binary translation work wasn't novel, please be specific about how these peer-reviewed bodies got it wrong. [1] https://www.vmware.com/pdf/asplos235_adams.pdf https://www.vmware.com/pdf/asplos235_adams.pdf [2] http://awards.acm.org/award_winners/bugnion_3886645.cfm http://awards.acm.org/award_winners/bugnion_3886645.cfm
- mcguire 12y agoThe ACM citation indicates that virtualization was first explored in the 1960s; Adams and Agesen's paper cites a 1974 paper: "Popek and Goldberg's 1974 paper [19] establishes three essential characteristics for system software to be considered a VMM:[...] In 1974 a particular VMM implementation style, trap-and-emulate, was so prevalent as to be considered the only practical method for virtualization.... We review basic obstacles to [trap-and-emulate] of the x86 architecture and explain how binary translation (BT) overcomes the obstacles..." In other words, the contribution of that work was an implementation technique for virtualization. In fact, that particular paper exists to compare binary translation to trap-and-emulate hardware support that had recently been added to the x86 architecture. Their conclusion is that sometimes one is better, sometimes the other. Look, I'm not saying binary translation wasn't new, or that it didn't change the face of computing as she is known---which is what the award was given for: "VMware Workstation 1.0 spurred a shift to virtual-machine-based architectures, allowing users to efficiently run multiple operating systems on their desktops [, and allow] large-scale data-center operators [to] increase the efficient and safe use of shared computational resources." I'm not even arguing that it didn't open up cool new research areas; I'm going to go play with unikernals as soon as I get a chance. (Even though that is a return to pre-timesharing systems.) But we're still talking about using virtualization to run legacy operating systems on modern hardware. Just like VM/370. init cms