http://www.drdobbs.com/jvm/232901227?itc=edit_stub groklaw comments http://www.groklaw.net/article.php?story=20120501005843202 I would say we have reached the end of the road for 'Programming as a Platform' -- the sort of package deal you get with Java or dot-Net. By Platform I mean giant APIs, 100s of dlls or shared objects, massive build systems to assemble anything, and IDEs to hook it all together. For any number of reasons, we are going to roll back the clock and re-implement these huge ecosystems *again*, likely in C or C++, so that they run well on mobile devices, tablets, parallel GPUs, big data map-reduce clusters -- all of which need raw speed, low overhead, and wicked fast code when it runs on the metal. Highly virtualised, to be sure, but then don't forget even the Intel CISC instructions are themselves virtual and microcoded. Google's Android is failing in the marketplace anyway -- meaning profits, not marketshare. It's losing money on Android every quarter (the judge in this case revealed -- a relevant point for damages based on profit!). As of now, the iPhone and Samsung are only models *making money* in the economic sense, rather than geeky wishful thinking. Closed devices with near proprietary code means we leave behind 'portability' and go back to the bad old days of hand coding the fastest, lightest weight. Orca sized libraries and up will now be hunted to extinction by patent and copyright trolls. Perhaps a few will be kept in zoos run by the likes of Microsoft or Oracle, at great expense.