4 ms·
I sense some wishful thinking here. WA will supplement JS not replace it. You'll have a canvas and that's it, but with the JS interface I can see how some peopl
by kowdermeister 10y ago
I sense some wishful thinking here. WA will supplement JS not replace it. You'll have a canvas and that's it, but with the JS interface I can see how some people will try to abuse it.
You can get rid of JS's shortcomings for years now with compilation. That's not really the goal here. What I see here is low level access for raw power. Most of the JS apps don't really need it.
Edit: I take it back. According to this note, I don't see what would stop anyone avoiding JS at all.
http://webassembly.org/docs/gc/#webidl-integration http://webassembly.org/docs/gc/#webidl-integration
- binji 10y agoThere is a FAQ entry on this point: https://github.com/WebAssembly/design/blob/master/FAQ.md#is-webassembly-trying-to-replace-javascript https://github.com/WebAssembly/design/blob/master/FAQ.md#is-...
- kowdermeister 10y agoThat's what I remembered and I answered based on that before the edit. Once you can reach the DOM API directly from WA code, JS is redundant for you can use for example C# to build apps. I hate to sound alarmist, but we might look back at 2012-16 as the years when frontend tooling was easy :)