We live in times where you learn JS to write server side code and desktop apps (electron), and you also learn C++ / Rust to create browser apps.
...
For further actions, you may consider blocking this person and/or reporting abuse
It's a bit of a nitpick, but
Unity uses C#, and it's already multiplatform. Right idea, but maybe not the right example. A more direct example would be the existing port of the Doom 3 engine(which is C++) to wasm.
There's also a lot of caveats being discussed. Among them, a growing tendency for organizations to disable wasm by default due to it's abuse by nefarious crypto mining implementations. Not a showstopper, but it can be a concern to resolve before making wasm an integral part of your application (potentially without fallback).
Wasm is definitely exciting (perhaps moreso outside the browser, for me), but there are some thorns to worry about on this rose bush.
Ahh right! Thanks for pointing it out.
Great view about the possible not so good things about wasm, keeps the whole sentiment balanced!
My pleasure, I'm glad it wasn't received as too negative.
The more you and others like you produce these articles and spread awareness, the more people we'll have to help shepherd the future of wasm. There's so much great potential to be realized.
Agreed! π€©
WASM is awesome, is multi-threading ready yet? I can't wait to be able to code some super efficient multi-threaded module in rust and just call it from js. Also, electron apps could benefit greatly from this.
This is a very interesting discussion. Anyone that have tried to build a desktop application with both: native bindings and css/html/js knows how delightful the experience of designing something with CSS is vs native bindings. This is one of the main reasons why electron apps tend to be more visual appealing and explains their increasing growth in the market (besides them being multi-platform, ofc).
WASM is a step in the right direction and could greatly improve the developing (and user) experience of desktop apps
Maybe there's a specific point about multithreading im not giving enough weight, but Electron apps are already benefiting from using Rust.
Discord uses it in their client (noted here though sparse on details; not the focus of that article). Aside from wasm, you also have the option of compiling a native node module. Example. And there are other ways to call a separate binary to do work that isn't ideal for Js.
Personally I didn't find the neon bindings any harder than wasm-bindgen, and in my use cases thus far I haven't had a reason to prefer wasm. It's a cool option to have though!
Wholeheartedly agree on the ease of web style gui development compared to other options.
Yes, multithreading has been stable for some time now. Recently I wrote a guide on configuring and using it from various environments: web.dev/webassembly-threads/
Yes agreed! WASM is really exciting and a lot more people can now contribute towards web!
Also give this a read: rustwasm.github.io/2018/10/24/mult...
Hey, itβs good to be back. Thanks for having me. Iβm really excited about this topic today as well. Rituel Vaudou Pour SΓ©parer Deux Personnes
Great post
Thank you so much π€©
Can't wait for more tutorials that actually interact with DOM.
this is so cool, i just know today that we can basically create wasm script using other language than rust thanks for the info
Yeah WASM is really cool!
Thanks for the appreciation π
Deno runs wasm natively. C# can as well (nuget package). it isnβt just a front-end technology. I am curious if there will be a RISC-V open source processor that can run it via hardware.
test