@[email protected] to TechnologyEnglish • 11 hours agoA peek into a possible future of Python in the browser - Łukasz Langalukasz.langa.plexternal-linkmessage-square12fedilinkarrow-up145arrow-down12cross-posted to: [email protected]
arrow-up143arrow-down1external-linkA peek into a possible future of Python in the browser - Łukasz Langalukasz.langa.pl@[email protected] to TechnologyEnglish • 11 hours agomessage-square12fedilinkcross-posted to: [email protected]
minus-square@rockSlayerlinkEnglish2•10 hours 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.