Connecting the dots - Scripting in 2005 Although it's a year old, this is a very interesting read on the .net Microsoft strategy. [Miceda]
Scary reading, though a clever strategy. MS are the experts in creating, maintaining and extending software monopolies. The common runtime could be a problem for all the various scripting languages out there. Though at least they'll leave Java alone won't they?...
This common runtime strategy seems spookily similar to the windows API strategy that MS used to crush pretty much all their competitors (like IBM (OS/2), Lotus, WordPerfect, Borland, Corel) in the desktop & developer software world and effectively turn developing software for Windows into a monopoly.
Get folks to write to their API that they control. Make some mumbles about maybe it being cross platform one day, maybe, through partners. Dick with the APIs whenever they like to put any competitors at a disadvantage, keep the good internal stuff for MS products or at least hold it back so that MS are always one step ahead, then when its got enough traction, crap all over the non-windows implementations.
I guess they're trying the same thing all over again to try move people away from Java and locked into MS again. But are people that stupid not to see exactly the same play all over again?
Just had another thought. We've got Jython, Rhino and Jacl (Python, JavaScript and Tcl? for the JVM). So why can't the JVM be the non-proprietary common runtime platform for scripting languages to share? I wonder what extensions to the JVM would be required to really support all languages and all platforms.
9:05:00 AM
|