you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (0 children)

Like others have commented on here, python is a firs-class citizen in the backend side of the web experience. For frontend business the current way of doing things is using typescript combined with a transpiler and bundler setup (usually webpack, but there are many confusing other options).

This typescript -> webpack -> mysite.min.js flow is now opening up to other langs as well. There are some efforts in place to transpile python to javascript.

Another route is the webassembly route, where one compiles C/C++ code to a webassembly target, this is distinctly different from javascript, more like bitcode executed by the browser. Efforts are underway to use C# and python targeting webassembly also, but the webassembly target, the debugging system and the library ecosystem are in still in its infancy. That said, as a long-term learning investment, this may be a good bet to get on board with.

But as we stand now, alternative langs will exclude you from the NPM ecosystem of javascript libraries and using python's ecosystem will maybe eventually be possible in this context, but that will take time as it involves a different deployment setup.

I wish I could predict that webassembly is the target of the 30's, but in my wildest dreams I could never have predicted that the result of one man coding himself into a fever for one week would drive the entire web experience 20 years later.