4 ms·
it's systematically translating the PyPy interpreter to the Javascript, so it has to get semantics right. However I'm not sure if the drawbacks can be addressed
by fijal 11y ago
it's systematically translating the PyPy interpreter to the Javascript, so it has to get semantics right. However I'm not sure if the drawbacks can be addressed in the current JS model, notably: very slow warmup, huge download size (that's primarily PyPy fault though), the lack of good JS access.
- jychang 11y ago> However I'm not sure if the drawbacks can be addressed in the current JS model, notably: very slow warmup, huge download size Only for the first time loading it. It would be great if some big organization (looks at Google) hosts the "standard" version of the file, much like jquery, so that it would be cached and ready to be used on the local machine most of the time.
- fijal 11y agoI believe this only addresses the download size and not the crazy warmup (you still reparse it etc.)
- TazeTSchnitzel 11y agoNot quite. At least Firefox caches compiled asm.js.
- fijal 11y agoYou can't cache JITted code (so JIT produced by pypy.js) because it'll be different each time.
- TazeTSchnitzel 11y agoAh, sure.