I suspect webassembly will fail miserably. If it succeeds anywhere it will be for gaming applications. I could be totally wrong, but most web developers who build applications and sites will not be likely to embrace this given the leverage JS provides and the simplicity of use.
Again, I am not extremely against wasm, but this writeup is pretty well done and my take away was that it was non-trivial to pickup, buggy and has poor documentation. I am curious who web assembly is for and who is really excited about it. Is it gaining traction in gaming, and also what am I missing(serious)?
edit: Can advertisers bypass content blockers by compiling to wasm?
We (at Stack Overflow) have a new documentation product coming down the pipe with an emphasis on examples and I thought it would be awesome if we could expand our stack snippets feature to languages beyond javascript. A reproducible example right there on the webpage. In researching existing solutions, nothing was satisfying, and then I had the idea to just use asm.js and write an MSIL interpreter. I spoke with some people familiar with asm.js and decided that it wasn't particularly difficult, but it had a ton of limitations from js file sizes to ways to get all of the libraries people ask about uploaded, and of course regular breaking changes in the browser. Wasm seemed like it could help with some of the issues being a formal web specification with representatives from multiple browsers.
Other than that, I can see a lot of uses for it, from small neural nets in the browser to high performance applications like photo editing, and of course gaming. It might not be for all applications, but it certainly has a spot.
Great writeup. I am a big proponent of the idea of webassembly as I believe many are. The browser is one of the greatest apps, and it is easy to look past many of its flaws because it provides a universal environment to develop for. I have always been a harsh critic of the balkanization apps provide when they are unneccessarily trying to extend functionality already provided by the browser and live natively on my device providing virtually nothing but more access to "my" resources.
That said, while I don't love writing apps in an old IBM GML and pulling in heaps of scripts to get the functionality I need, it is easy and well understood (which is why it has proliferated). If we are to change this, I think an entirely new paradigm would be easier to use and embrace than something like wasm because the browser has a lot of access to resources and this has a fairly narrow use-case relative to it's complexity.
I could be wrong, as this technology is super nascent and people as intelligent and synonomous with the web like BRendan Eich are openly supporting it, I just don't see it being embraced at the sort of tipping point neccessary to proliferate.
It will be very hard to build a community of people doing things like you have here: providing great resources and tutorials and a community of code base to build on. A new standard or tech must be 10x better than the current one and I do not feel this is.
Also you can't trivially copy/debug a web component built using web assembly(so far) and play with it which is kinda a death sentence for any tech on the web unless it's championed as being a killer tool for some usecases-which this doesn't seem to be so far
WebAssembly will eventually have access to the same APIs as JavaScript does now. Then it's just a matter of using an ES2016->wasm compiler rather than an ES2016->ES5 compiler.
The idea is that we will be able to write web applications in a sane, proper language like C# or similar, and then compile to Web Assembly. I, for one, embrace this idea whole heartedly.
I can respect that. However, my point is, are you a web developer who primarily writes code for the web at your day job. Anecdotally, I haven't seen a lot of overlap between people writing web applications and C# developers. I have seen a lot of C family devs think this is awesome, but have no plans to actually develop directly for the front-end web.
edit: the first major demonstration was Unity's angry bots according to Wikipedia. So it appears this is for game devs, and game developers who want to build for the browser will be excited about this. I just think webassembly to be really far down on the ist of improvements we should make to the browser.
Web Assembly is exciting to me precisely because I'm not a web developer, and the whole idea of being a web developer as distinct from any other kind of developer is a bit absurd, especially considering the ubiquity of the web and the fact that it basically means you're a JavaScript programmer of some variant. Your language choice shouldn't determine your infrastructure.
> You language choice shouldn't determine your infrastructure.
Of course. I am a js dev and work mostly with nodejs. However, I would push back here and say that JS is the only real choice for web development as you must code for a browser which most often interprets html/css and js. So not surprisingly, and especially with the proliferation of nodejs, all the people writing code for the web are javascript programmers. React, Angular, VueJS, Meteor ect all provide rich javascript frameworks/libs for writing web applications and a full stack can be written with a single language.
My point is that asm.js seems to provide a lot of leverage as an option and internet speed and machi ne resources also are improving. I would not say that the web, the browser or the current situation is ideal-- far from it, but webassembly seems like a very small improvement patch. It basically allows games devs who want to code specifically for the non-mobile browser to have slightly better performance by learning a very obtuse new language paradigm that is brand new.
- It doesn't improve on marking up apps in IBM markup language from the 60s which was originally developed for research papers.
- It doesn't improve security. I think it may actually be net bad for security given the obfuscation.
- It is targeted at a very narrow community
- It is largely embraced and championed by people who do not currently write web apps. It is unclear if their enthusiasm will carry over to them actually coding in it.
The web ecosstem is horribly broken. I would love something as innovative as javascript to come along again, when Eich put Scheme into the browser people were very excited. They could do something new and 10x better than previously possible. Given that there are such glaring problems in with the web right now (and I do admit performance is one of them) this marginal improvement, if indeed it proliferates and in fact does improve things, seems so minimal at a pretty steep cost to learn it, that I don't find it exciting and expect it to have virtually no impact.
They should do so much more than this. Imagine even if browser companies put a python or ruby interpreter (or even a native c++ one) into the browser. Imagine all the possiblities of adding natice scss support, limiting or removing very old unused feature support and refactoring the codebases. ect. Imagine not using 1960s era research paper syntax to write a web app. There is so much room for improvement that making something that requires me (and so many others) how to write applications for very little benefit will be met with crickets. or extreme enthusiasm from people who don't write web apps and never will, but find it reminiscient of their mem-mgmt c-like language they use for mobile or systems programming.
You could say the same thing about any assembly language though. But they are still important, even if only a few people need to truly master them. The main advantages web assembly should provide are that it be a simpler target for compilers, minimizes overhead for doing so, and that its performance be independent of that of a higher-level-language like javascript.
All the things you want require a standardized, performant web assembly to meaningfully and portably implement.
I would rather have a permanent top-level tracking banner section built right into my browser as long as I don't have to write JS anymore. It's very high on my priority list.
I suspect wasm is a long-term bet on the part of web advocates (including Google and individuals like Eich) to ensure the web remains center stage in the age of mobile native apps that sit on top pretty powerful mobile hardware. As I understand, it's essentially asm.js repackaged in a more formal, standardized manner and has already gained support from all the major browser vendors.
Once integrated properly in desktop and mobile browsers (maybe two years from now), it would probably reduce most of the "useful" performance lead that native apps have over web apps. But, it's still a bet - because of course, no one really knows for sure what things will look like two years from now.
Speaking as a front-end-heavy developer (but someone who knows quite a lot about the back end too), the ideal of WebAssembly definitely excites, but the bridge to actually engaging with the technology is too cumbersome to actually do anything with it yet.
My take is two-fold. First, the tooling needs to mature. Second, a community of more hard-core developers (i.e., those who work regularly with C, C#, C++, etc.) needs to crop up.
Without those two things, I think you're right, it will never take off. But my bet is that both of those things happen; larger companies will at some point bank on it, and throw a bunch of tooling and development resources at it. Just a guess.
Java applets ran through browser plugins that sidestepped the sandboxed browser environment that keeps users secure on the web. This would be an assembly level compile target for the Javascript VM instead.
Again, I am not extremely against wasm, but this writeup is pretty well done and my take away was that it was non-trivial to pickup, buggy and has poor documentation. I am curious who web assembly is for and who is really excited about it. Is it gaining traction in gaming, and also what am I missing(serious)?
edit: Can advertisers bypass content blockers by compiling to wasm?