|
|
|
|
|
by krapp
2232 days ago
|
|
WebAssembly's best case scenario is "native software compiled to run to the web." Unlike Java applets, WebAssembly isn't tied to a specific language or runtime, so that "smidge" in the case of being inclusive of so many languages is pretty big. You could even run Flash sites in WebAssembly, the only thing stopping that from happening is copyright law. It would probably be even safer and run faster than Adobe's plugin. |
|
I dunno, I don't get the point. If it gets rid of the dumpster fire that is JS applications, good, but it'd be better if the web could be for documents and applications could be for applications.
I'm too cynical and I've seen too much to believe that it'll be silver bullets and rainbows.
The write-once, run-everywhere idea always falls down, and pushes everything to lowest common denominator shovel-ware.