richmassena23
How many more reimplementations of basic functionality on the major desktop environments do we need? It seems like whatever the current window manager is, and however well it works, it'll be thrown out and a new one will take it's place, and take a few years to do what the old one did. We'll throw out the audio stack again at some point. X isn't good enough, so we'll throw that out. Since Wayland isn't network transparent, there will be twelve different ways to add it back in and five incompatible ways to run old X applications on top of it. When those aren't sufficient, we'll throw it out again and start over, ad nauseum. And this applies to most things on the system that are "good enough".
Linux on the desktop is stuck in the 90% category, where 90% is implemented (and as we know, this represents 10% of the work). It's always tempting to avoid the unsexy 90% of the work and write from scratch. The end result is throwing increasing amounts of the baby out with the bathwater.
What appeals to me most about this article is the idea that a team's performance can be measured somewhat objectively. What remains to be seen is whether the team with the highest performance on the artificial tests yielded better performance in real-world scenarios.
If it's possible to put together a good team based on simple tests, it would be beneficial to every organization.
LISP machines were extraordinarily expensive for a single-user machine, much of which was due to the heavyweight hardware (like 32-bit processors, 32MB of RAM and fast high-capacity disks in the 1980s).
If I recall correctly, your basic Symbolics LISP machine, with software, cost about $50,000 in 1986. According to an online inflation calculator, that's $96,500 in today's money. I can guarantee that the resulting 64-core 128GB machine with 1TB of SSDs in RAID-10 configuration would beat the pants off of the Symbolics workstation, use less power and make much less noise and you'd have money left over.
All that said, interface responsiveness is part of the user experience. If your application/OS/device crosses that threshold were the user has to wait, it's a failure. People only stick with Word for Windows (surely the unnamed word processor referenced) because they don't know better or have a choice.