5 ms·
WebAssembly has different ambitions than Flash. It is meant to be become similar to an operating system, whereas Flash was a very specialized tool. TinyGo and
by jedisct1 6y ago
WebAssembly has different ambitions than Flash. It is meant to be become similar to an operating system, whereas Flash was a very specialized tool.
TinyGo and Zig can generate .wasm files out of the box.
- pjmlp 6y agoThe ambition to delay progress for 10+ years. Good to know that at least two do so, even though Zig isn't even 1.0 and TinyGo is well tiny Go subset.
- emteycz 6y agoWasm did nothing to delay progress. It's a bunch of people doing what they think is cool and useful, and they're pretty upfront about it. If you don't like it, why are you waiting for them; they're not slowing you down. What did you do?
- pjmlp 6y agoIt surely did, given that we had Unreal running on Flash in 2011, with a 3D API that WebGL 2.0 still fights to achieve the same level of guaranteed hardware acceleration. All in 2011, 10 years ago! What did I do? Contribute to native apps taking over. Unfortunately a lost battle now that ChromeOS has won the Web.
- emteycz 6y agoWhat does that have to do with Wasm people? They're working on Wasm and you're working on native apps. If you desired a better Flash, then you should've made it, the Wasm contributors are not responsible for your desires. Unfortunately for you nobody picked it up, but that is not fault!
- pjmlp 6y agoThe same group of people actively botched Flash and PNaCL support on browsers.
- emteycz 6y agoPlease send links to discussions/commits. I remember it as these technologies being inherently botched and pretty much unbotchable, and the group moving on to Wasm - which isn't a fault they could be blamed for, they're not yours to command. I'm very sure that if you knew how to unbotch it you could've simply submitted into the discussion and would've been accepted.