A peek into a possible future of Python in the browser - Łukasz Langa

My Python code was too slow, so I made it faster with Python. For some definition of “Python”.

12 comments

Please please please can we just use type safe languages.
- Agreed. Just the idea of finally replacing JS with something only to be another of those "dynamic" languages makes me want to puke.
  
  Asking genuinely as someone who knows not much about this subject, is typescript not already an option? Isn’t it just type safe js that gets interpreted as js?
This isn't about replacing javascript, this compiles something that looks a bit like Python to C and then to WASM. Which browsers can run natively these days. But you can do that with any source language if there's a compiler for it, type safe or not. You can compile Rust to WASM too for example. So nothing's getting replaced, these are just additional tools for Web developers.
I think if the idea is to replace js, it should be a superset language at the interpreter level. I.e. the interpreter can run js, but valid js wouldn't work with the compiler. It makes it a drop-in replacement without harming legacy
- WebAssembly is the target, not js, I believe.
Very interesting.

12 comments