Ask Lemmy

26980 readers

1392 users here now

A Fediverse community for open-ended, thought provoking questions

Please don't post about US Politics. If you need to do this, try [email protected]

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 [email protected] or [email protected]. 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 [email protected]. 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

founded 1 year ago

MODERATORS

[email protected]

candyman337

[email protected]

What is the current state of webasm? (gregtech.eu)

submitted 2 weeks ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

When will we be able to use any programming language in the web?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 15 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

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.

[+] praise_idleness 7 points 2 weeks ago* (last edited 1 week ago) (3 children)

[deleted]

[–] [email protected] 7 points 2 weeks ago (1 children)

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.

[–] [email protected] 4 points 2 weeks ago

react is slow

[–] [email protected] 5 points 2 weeks ago

JS is not slow.

Since JS is single threaded it can be pretty slow compared to anything being able to use multiple threads

[–] [email protected] 1 points 2 weeks ago* (last edited 2 weeks ago)

JavaScript is slow if you need to do things that JavaScript can’t do, such as

lots of stack-allocated objects/arrays (in JavaScript you have to heap-allocate them)
hash maps with non-primitive types as keys (in JavaScript you have to serialize them to a string)
count trailing zero bits (in JavaScript you have to use a lookup table)

[–] [email protected] 7 points 2 weeks ago

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:

Same language and similar tooling as in the backend. Most libraries work the same way (obviously excluding libraries that read from the filesystem, for example). This is especially good, if you've got lots of "full stack" devs.
Same model classes as in the backend. If you change a field, the compiler will force you to fix it on both sides. It is compile-time guaranteed that backend and frontend are compatible.
Rust is a nicer language than JS/TS. I find especially Rust's error handling via Result and Option types + pattern-matching works really well for UI stuff. You just hand the Result 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.
Having a strict compiler makes it less bad when you're lax on testing, and frontend code is a pain to test.

Cons:

If you've got pure frontend folks, or people who are deep into React or Angular or whatever, those are not going to be as productive.
The JS ecosystem is massive, you just won't find as many component libraries for Rust, which can definitely also reduce productivity.

With me being in a team with few frontend folks, I would definitely opt for it again.