Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Right now. WASM has been supported by every browser for a while now, and most webapps are made with WASM. That said, it's not a replacement for Javascript, most people only use it on things that need to be high performance like heavier apps and web games. Nobody really makes websites that rely on WebAssembly instead of JS to my knowledge.
We've got a WebAssembly web-UI at $DAYJOB. Implementation language is Rust, we use the Leptos framework (although other mature frameworks are available for Rust).
Pros:
Result
andOption
types + pattern-matching works really well for UI stuff. You just hand theResult
value over to your rendering stack and that displays either the value or the error. No unset/null variables, no separate error variable, no ternaries.Cons:
With me being in a team with few frontend folks, I would definitely opt for it again.
From my understanding, it’s because WASM is pure (deterministic) and needs stateful entry points in order to work. For this reason, a JavaScript bit to interact with it is a requirement at the moment.
Also WASM can't directly manipulate the DOM so it can't really be used for handling HTML/CSS, all front-end stuff still has to be done with JS.
While it’s true you can’t do it in WASM directly, there are frameworks that interoperate between WASM and JS, such as Yew
One only needs to create an interface between them, since WASM is capable of calling JS functions. DOM manipulation then becomes as simple as calling a function in your language of choice, such as with web-sys
Important to note that WASM will only give you enough performance boost to justify using it if the task is significantly demaning to JS. JS is not slow.
JavaScript is slow if you need to do things that JavaScript can’t do, such as
JS is slow, but I program Rust and Scala. Every internal app at my company is react based and I spend most my time waiting for that bloated framework to load a simple table. It can take seconds to load a 20 route paginated table from source.
react is slow
Since JS is single threaded it can be pretty slow compared to anything being able to use multiple threads