Bundling as standard your own proprietary plugin which you know no one else will bundle is definitely not pushing innovation, and is little different from ActiveX, DirectShow filters, VBScript and the rest.
Re:Script type="text/python"
by Raphael_Amiard on Tuesday July 20, 2010 @03:36AM
(#1531428)
Well my first reaction is the same as yours, but since python is OSS the possibility does indeed exist that this could be emulated amongst other browsers without needing Silverlight.
The runtime API they present to python though, while it seems to be just the DOM exposed, would still need to be documented and standardized.
But IronPython is FOSS. The fact that it is being bundled in a closed source plugin seems like an implementation detail to me. If Firefox wanted to they could expose this very same implementation of a python runtime engine.
Dear god, this, yes.
Just embed CPython...
I imagine that, from a security standpoint, embeding CPython in a browser would be pretty hairy.
I would say that Microsoft 'pushing innovation on the browser front' is the root cause of most browser related developer headaches over the last 10 years.
While Ajax has certainly caused headaches for me, it's probably the best thing that's ever happened to the web... and we can thank Microsoft for it.
Ah but XMLHttpRequest was introduced in 1999. I said, very carefully, over the last 10 years..
I can see Firefox following suite. Just embed CPython and route it through that; given that they are struggling to match the Javascript performance of V8 it seems they might welcome a free diversion.
Chrome following suite is more questionable. V8 is the current king of the ring in JS performance, but Google is widely known to be a supporter of Python. I can imagine them amiable to the idea of unifying their server side glue with the client. Besides; they have shown time and time again to make 'strategically strange' moves in order to help advance the general state of the internet. When it comes to google if the internet wins, they win.
Opera would be wise to support it as a differentiating feature. They need all the tricks they can pull to stay relevant.
The bugaboo to me is Apple. They have Nitro, which is right up with V8 in most benchmarks, and support for languages which have benevolent dictators living in their enemy's quarters doesn't sound like an Appleish thing to do. I doubt they would peacefully hand over any control.
Of course if we do stumble into a multi-client-side-language-choice Renaissance it will be Adobe with the most to lose.