@[email protected] to [email protected]English • 3 days agoA peek into a possible future of Python in the browser - Łukasz Langalukasz.langa.plexternal-linkmessage-square12fedilinkarrow-up154arrow-down12cross-posted to: programminghackernews
arrow-up152arrow-down1external-linkA peek into a possible future of Python in the browser - Łukasz Langalukasz.langa.pl@[email protected] to [email protected]English • 3 days agomessage-square12fedilinkcross-posted to: programminghackernews
minus-square@[email protected]linkfedilinkEnglish2•3 days agoI 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
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.