Asklemmy

47161 readers

683 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 6 years ago

MODERATORS

[email protected]

since almost everybody I encounter here agrees that Javascript sucks, What should I learn to make good "web apps" with good performance ? (lemmy.dbzer0.com)

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

33 comments fedilink hide all child comments

Here sucks is in the sense of suckless philosophy, I don't think everybody likes the suckless movement but I've seen that many people, me included, don't like how modern web apps look like (messenger and tiktok are like the worst). So if I want to make interactive web apps, what are the better technologies to not make the web shittier ?

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

[–] [email protected] 3 points 2 days ago (1 children)

Webassemby is still limited to a single thread as far as I'm aware, so it's not a full runtime for the language you are writing in as anything using threads behind the scenes tends to fall over unexpectedly at runtime.

Its also an absolute bastard to debug (young ecosystem)

[–] [email protected] 3 points 2 days ago

Yeah, I doubt WebAssembly when executed in a browser will become multi-threaded anytime soon, since JavaScript is single-threaded just as well. If you need multiple threads, you need to use web workers. Haven't done anything with those yet, but I'd assume them to be usable from WebAssembly as well, since the whole JavaScript API seems to be accessible.

Well, and in Rust, I'm pretty sure the runtime that's typically used for async stuff (tokio) will produce a compile error, if you try to enable the "multi-thread" feature flag on the WebAssembly target.
But yeah, might be more of a problem with other languages.