3 ms·

This looks really old. It doesn't even mention anything about Python 2.7, let alone 3.x. Shouldn't we date the post? Also, I think we have come a long way sinc

by mizzao 11y ago

This looks really old. It doesn't even mention anything about Python 2.7, let alone 3.x. Shouldn't we date the post? Also, I think we have come a long way since the jQuery/AJAX spaghetti that was apparently a huge problem when this was conceived. I don't even think Node was a thing when this started. Things like Meteor and React address most of the issues and much more, such as live data and reactive UI.

andybak 11y ago
https://github.com/pyjs/pyjs https://github.com/pyjs/pyjs Last updated June 14 > Things like Meteor and React address most of the issues and much more, such as live data and reactive UI. They don't address one major issue - using a language of your choice. (I don't use this project but I keep an eye on all 'Python in the browser' projects' and the minute one looks mature and sensible with some real-world takeup I'll be all over it)
- mizzao 11y ago
  That's a valid concern, but I think ES6/ES2015 will help ease the pain of using Javascript.
  - andybak 11y ago
    It's really not about javascript getting better or worse - it's the fact that I don't enjoy coding in javascript anywhere close to how much I enjoy coding in Python. Javascript would have to morph out of all recognition for that to change. I'm sure other people feel the same about their language of choice too. I'm hoping WebAssembly will open the floodgates for genuine choice in browser scripting.
- dan_blanchard 11y ago
  That update was just a README update. Most of the files in the repo haven't been touched in over 2 years and they haven't done a release since 2012.
  - andybak 11y ago
    Damn. In that case - on a related theme: https://github.com/skulpt/skulpt https://github.com/skulpt/skulpt https://github.com/brython-dev/brython https://github.com/brython-dev/brython