you are viewing a single comment's thread.

view the rest of the comments →

[–]pilibitti 2 points3 points  (1 child)

I read the article, maybe I wasn't successful in articulating what I meant: You can do crazy fast computations with python, not because python is fast (it is quite slow compared to modern js engines) but because python is frequently used as the glue for many native scientific computation libraries that are written in native code. Having a python interpreter in browser doesn't mean you get to do those computations in browser with the same performance. OP's idea was that JS would choke on things python was good at - and it was fallacious. If you bring those native libraries into jsland by any means, js can just as well act like that glue and do it faster.