Message366375
you can add
* https://github.com/pmp-p/pydk/tree/master/sources.em/Python-3.8.0b4.patchset -- Python 3.8.x
(wasm not asm.js, clang-10+ required)
demo https://pmp-p.github.io/python-next/test.html
CPython can already run in the browser with very little patching, but major issues are :
- asyncify'ing the whole wasm VM to have pre-emption over cPython's one to prevent blocking I/O slows down things *a lot* (10x)
=> (very?) bad user experience.
- the size of vm + stdlib ~ 30 MiB and wasm compilation time.
=> bad user experience on first load or slow connexion.
- the lack of threading in wasm MinimumViableProduct specification (but this is the browser standard for now), that leads to rewrite bits of stdlib ( like eg asyncio module )
=> adding more maintenance burden on stdlib (!)
i tested them all and my personnal opinion is : I can see no use case that would favour "stock" cPython wasm versus a blazing fast MicroPytho (or pycopy) wasm flavour or supercharged full stack pyodide. |
|
Date |
User |
Action |
Args |
2020-04-14 08:58:34 | pmpp | set | recipients:
+ pmpp, serhiy.storchaka, xtreak, Simon Biggs |
2020-04-14 08:58:34 | pmpp | set | messageid: <1586854714.62.0.586609535151.issue40280@roundup.psfhosted.org> |
2020-04-14 08:58:34 | pmpp | link | issue40280 messages |
2020-04-14 08:58:34 | pmpp | create | |
|