3 ms·
Well I'm in favor of things running in a sandbox, especially random code delivered over the internet and run automatically in my browser. But aside from that, W
by sp332 9y ago
Well I'm in favor of things running in a sandbox, especially random code delivered over the internet and run automatically in my browser. But aside from that, WebASM has a flat memory model and (so far) no built-in garbage collection. It has very few features, it's very fast to parse and it runs fast too. Even the asm.js version was fast back in 2013 https://hacks.mozilla.org/2013/12/gap-between-asm-js-and-native-performance-gets-even-narrower-with-float32-optimizations/ https://hacks.mozilla.org/2013/12/gap-between-asm-js-and-nat...
As for the rest, I don't know how you're measuring. Photoshop runs a lot faster than programs on my Centris 610 did, and sure it's a bloated mess of different programs glommed together but guess what, it does a lot more than smaller programs do. Your comment counts the cost of everything and the value of nothing. You can't click a link and get a brand-new full-featured word processor running on an old Mac in 10 seconds like you can by clicking https://docs.google.com/ https://docs.google.com/ But I can run MacPaint in my browser thanks to asm.js https://archive.org/details/mac_MacOS_7.0.1_compilation https://archive.org/details/mac_MacOS_7.0.1_compilation
- analognoise 9y agoWe used to have that back in the day. It was called...installing, I think it was? Then the app...'program'? That was It! Program! Ran at native speed. Amazing how we ever got anything done without carting around an entire browser as an attack surface.
- sp332 9y agohttps://xkcd.com/1367/ https://xkcd.com/1367/ I don't think I understand your comment about attack surface. A Chrome sandbox is a lot harder to attack than a Mac Classic installation - or pretty much any current method of "native" installation.