A very interesting talk by Rob Pike on Systems Software Research is Irrelevant".
Some quotes from the slides (by Rob Pike):
"We see a thriving software industry that largely ignored research, and a research community that writes papers rather than software".
"Java is to C++ as Windows is to Machintosh: an industrial response to an interesting but technically flawed piece of systems software."
"Linux's cleverness is not in the software, but in the development model, hardly a triumph of academic CS (software engineering) by any measure."
"It (systems research) is just a lot of measurement: a misinterpretation and misapplication of the scientific method. Invention has been replaced by observation."
"If it didn't run on a PC, it didn't matter because the average, mean, median, and mode computer was a PC."
"To be a viable computer system, one must honor a huge list of large, and often changing, standards: TCP/IP, HTTP, HTML, XML, CORBA, Unicode, POSIX, NFS, SMB, MIME, POP, IMAP, X, ... With so many externally imposed structure, there is little left for novelty."
"Commercial companies that 'own' standards deliberately make standards hard to comply with, to frustrate competition. Academic is a casualty."
"New employees in our lab now bring their world (Unix, X, Emacs, Tex) with them, or expect it to be there when they arrive... Narrowness of experience leads to narrowness of imagination."
"In science, we reserve our highest honors for those who prove we were wrong. But in computer science..."
"How can operating systems research be relevant when the resulting operating systems are all indistinguishable? (Unix is) a victim of its own success: portability led to ubiquity. That meant architecture didn't matter, so there's only one."
"Government funded and corporate research is directed at very fast 'return on investment'... The metric of merit is wrong."
"Measure success by ideas, not just papers and money. Make the industry want your work."
"The future is distributed computation, but the language community has done very little to address that possibility."
My take on the lessons learned, again in the form of quotes:
"Keep the ideas flowing, even if the implementation is not feasible (using existing systems)."
"When thinking of distributed systems -- think beyond web, Browser and Flash Player"
"Something is popular, does not mean it is correct or best way to do that thing."
"Do not publish papers that fake measurement as research."
"Do not take a job that you are not truly motivated about."
"Writing software in Java is like writing detailed machine instructions. Learn Python instead."