Python in the browser

Silverlight... with "performance" stuff in C#? What kind of client-side scripting is going on that we need to push it down to C#?<p>Javascript does a great job manipulating the DOM, especially with Prototype and the like.<p>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.<p>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.

This was quite interesting, until, "This is because Silverlight is the Python execution engine."

And now, Python in the browser without Silverlight (i.e., on pure JS):<p><a href="http://www.skulpt.org/" rel="nofollow">http://www.skulpt.org/</a>

"Python in the browser" ... with Silverlight.

As much as I love .NET, I just can't get excited about Silverlight. When you require your users to install a new plugin, it raises the barrier to entry pretty significantly -- especially when you're talking about technical users.<p>Personally, I took a different route: I created a Python-&#62;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 find JavaScript and Python are more similar than they are different.<p>Coming from Python, learned JavaScript, felt right at home. (just have to remember the vars, {}s and ;s)

This is interesting in a very narrow niche. But even being a Python fanboy I'm more likely to bring JS into the server than Python into the browser. It just makes huge piles of sense.

1.5 MB, even if one-time only (assuming no cache-cleaning on client side), is quite heavy. Too heavy for vast majority of web applications.

What an ugly hack.