Python in the browser
blog.jimmy.schementi.com
blog.jimmy.schementi.com
Javascript does a great job manipulating the DOM, especially with Prototype and the like.
Having a stronger scripting language in the browser like python (even ruby?) would be great if it didn't come at a significant cost and increased performance. If you'd ask anyone who spends a significant amount of time writing js code, they'd want it faster. Not Python that is built on top of a proprietary engine (plugin based!), that uses... JAVASCRIPT to embed it.
On top of that, the python code looks semantically identical to DOM manipulation in Prototype. So really the only thing you've gained is "writing client code in python" while dumping proprietary formats and a huge initial download on your users. I'll excuse myself as sensationalist when I say that it seems a little selfish on the developer's part.
Personally, I took a different route: I created a Python->Javascript compiler with a real macro system. Allows me to quickly hack damn near anything together and keeps me away from JS (which I can't stand, largely for aesthetic reasons), without imposing anything at all on my users.
I mean, I don't do Silverlight either, but your reasoning seems suspect.
Coming from Python, learned JavaScript, felt right at home. (just have to remember the vars, {}s and ;s)
How exactly would you propose cramming a usable Python runtime into a download that was substantially less than 1.5 MB in size? On the OS X 10.5 box I'm sitting at right now, the 'libpython2.6.a' static library from my source build of Python 2.6 is over 6 MB. The actual 'python' binary is nearly 2 MB, and stripped of all debugging symbols, still comes in at about 1.4 MB.
If you had some really good compression, and included only a small part of the standard library, I can see getting a CPython package in around the 2-3 MB mark, but not much more.
E.g., for AlleyInsider, which occasionally shows up here: http://www.webpagetest.org/result/100318_6303/
(Nice tester from AOL - try your own cases)