News for hackers. Stuff that matters.

A comment on Skulpt: client side Python without preprocessing. Parent comment

Re:Skulpt: client side Python without preprocessing by meredydd on Tuesday October 31, 2017 @10:57AM (#15593680)
As Albert-Jan and I discussed at PyCon this weekend, the long-term future for Skulpt quite possibly involves compiling to WASM rather than Javascript. This is very unlikely to happen until every modern browser supports WASM. Neither Trinket's educational mission nor Anvil's "web apps for the world" mission are compatible with leaving users behind just because their workplace or school runs IE.

The runtime can be remarkably small (Skulpt is 228kb minified and gzipped, including the standard library), so I think it's a feasible target. (Pypy.js is, of course, enormous!)

[ Parent | on HN ]
Re:Skulpt: client side Python without preprocessing by steveklabnik on Thursday November 02, 2017 @12:08PM (#15611641)
> This is very unlikely to happen until every modern browser supports WASM

WASM ships in every evergreen browser today: http://caniuse.com/#feat=wasm

Only significant browser missing it is IE; only Edge has support.

[ Parent | on HN ]
Re:Skulpt: client side Python without preprocessing by albertjan on Tuesday October 31, 2017 @01:56PM (#15595135)
What @meredydd means is, leaving the compiler written in javascript but emitting wasm, so compiling python into wasm with javascript. Too many compilers! :P
[ Parent | on HN ]