WASM is to insert browser embedded another layer of cryptography that works fast, for things like embedded email, or opening a browser window to distributed computing, also it's for ability to compile things like statistics and graph algorythms and compression algorythms especially from C to javascript with implicit speed, sometimes you have to compress and have to transfer compressed data a lot in applications like cloud photo editor that edits raws in your computer, it's better to transfer it completed. Then there's javascript whole GL level, which is compatible, for making games, and also for making computings, like photo edits, quick edits, optimizing your posts on facebook shown location on your own computer instead of facebooks servers without you even noticing because dynamic javascript loading so you cannot even detect what is executed by brower therefore rendering possible facebook scale app to be localized only in currectly online computers from how efficient they are now, without one centralized server.
You heard it on bitcoin talk first.
Topic: Web Assembly (Read 648 times)
Quite contrary to what most seem to believe I'd say wasm will only strengthen javascript. At the end of the day most of the web will still use js, most libraries around "web'y" stuff will be js and wasm will help js overcome some of the performance limitations (and js VMs are already performant as far as dynamic languages go). Many of the wasm libraries will probably be designed with js-interop in mind. So while technically it may be easier than ever to use whatever you want to write your web thing I don't think many will for real projects.
I'd design it in the same way I would've designed it before WebAssembly got incorporated into major web browsers. The limiting factor isn't what we can do with the frontend - it's what the user can run on their machine. I somehow doubt that having a CPU intensive frontend would go over well with anyone who even occasionally browses the forum on mobile, tablet or perhaps a weaker laptop. Even then, WebAssembly is pretty much only useful for compute-heavy tasks - AFAIK it can't manipulate the DOM, which is something the wide majority of UI frameworks rely on. If you're looking for doing graphics related calculations (be it 2D or 3D), WebGL has already been around for much longer and offloads much of the work to the GPU - a device much more equipped to handle these type of calculations.
If we were to set aside performance considerations, gimmick focused software development often not only results in an inferior product (in this case, that'd be crappy UX) but ages incredibly badly (look at all the promotional pre-2000 demo disks that large corps used to give out or sell). Innovation for innovation's sake is an empty endeavor.
If we were to set aside performance considerations, gimmick focused software development often not only results in an inferior product (in this case, that'd be crappy UX) but ages incredibly badly (look at all the promotional pre-2000 demo disks that large corps used to give out or sell). Innovation for innovation's sake is an empty endeavor.
Finally a technology exist to create a fancy front-end with an actual language (coughjavascriptcough)
This means we can have a true web 3.0 experience from forum software.
for gamers; https://webassembly.org/demo/Tanks/
for nerds; they took javascript and made it able to process bytecode, so now we have fucking javascript "sandboxes" executing bytecode for frontend, meaning way more complex interfaces, and the major 4 browsers support this fancy javascript VM.
===
in other news golang has support in 1.11 to compile wasm
(if it were entirely up to me, i'd ditch http for gopher as the superior interface)
===
to everyone:
If you were to design a modern forum interface for a "new bitcointalk", how would you go about doing it with web assembler in mind? Meaning completely immersive, every bit counts web engine that can do pretty much as many movements as your underlying OS/platform.
This means we can have a true web 3.0 experience from forum software.
for gamers; https://webassembly.org/demo/Tanks/
for nerds; they took javascript and made it able to process bytecode, so now we have fucking javascript "sandboxes" executing bytecode for frontend, meaning way more complex interfaces, and the major 4 browsers support this fancy javascript VM.
===
in other news golang has support in 1.11 to compile wasm
(if it were entirely up to me, i'd ditch http for gopher as the superior interface)
===
to everyone:
If you were to design a modern forum interface for a "new bitcointalk", how would you go about doing it with web assembler in mind? Meaning completely immersive, every bit counts web engine that can do pretty much as many movements as your underlying OS/platform.
Jump to: