Maybe doing scientific stuff in-browser that you would normally need a Python backend (with numpy etc) to do. I don't see it being used for driving UIs.
Getting python running in the browser and getting to the point the packages people care about (torch, numpy etc) would work in the browser seems a huge leap.
You can't even package up a python application to work on an arbitrary machine with those libraries without a world of hurt and some quite laughable hacks, most distributed python software is started from a .bat file that installs a local copy of python not an .exe, the ones that are a single .exe (PyInstaller) unzip themselves into a temp folder every time they are run.
With how poor Python is at even distributing software written in it's home desktop environment to another machine it's going to be a large leap to get all that to work on another machine without in another environment. (Environment as in desktop/browser not venv wrapper)
Python seems so limited in where it can go by the ideological choice that it's installed into the base of the operating system rather than treating it's libraries as relative to it's scripts location. Entire ecosystem is built within wrappers just for this ideology.
Says a lot imho when it's easier to distribute a Javascript application to people than a Python one when JS was never intended to run outside a browser.
Hasn't Pyodide already made this leap? I know the pain of dealing with the Python runtime and packaging across machines, but in this case, the browser is providing a pretty uniform environment.
Comments
Maybe doing scientific stuff in-browser that you would normally need a Python backend (with numpy etc) to do. I don't see it being used for driving UIs.
Getting python running in the browser and getting to the point the packages people care about (torch, numpy etc) would work in the browser seems a huge leap.
You can't even package up a python application to work on an arbitrary machine with those libraries without a world of hurt and some quite laughable hacks, most distributed python software is started from a .bat file that installs a local copy of python not an .exe, the ones that are a single .exe (PyInstaller) unzip themselves into a temp folder every time they are run.
With how poor Python is at even distributing software written in it's home desktop environment to another machine it's going to be a large leap to get all that to work on another machine without in another environment. (Environment as in desktop/browser not venv wrapper)
Python seems so limited in where it can go by the ideological choice that it's installed into the base of the operating system rather than treating it's libraries as relative to it's scripts location. Entire ecosystem is built within wrappers just for this ideology.
Says a lot imho when it's easier to distribute a Javascript application to people than a Python one when JS was never intended to run outside a browser.
Hasn't Pyodide already made this leap? I know the pain of dealing with the Python runtime and packaging across machines, but in this case, the browser is providing a pretty uniform environment.