this post was submitted on 07 Feb 2026
51 points (98.1% liked)

Technology

80795 readers
5045 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] orclev@lemmy.world 1 points 11 hours ago

It's a workaround for the historical trash fire of JavaScript in the browser. Since nobody could agree on a way to do something other than JS in the browsers they came up with this gradual replacement where initially WebAssembly was just a special version of JS, then they turned that into a bytecode interpreter. The end goal was to let you use any language as your browser scripting language but the implementation isn't there yet. It's pretty painful to do anything with the browser APIs via WebAssembly because you're still using the terrible JS APIs rather than something more ergonomic for the language you're using and you need to write JS shims around all your non-JS code.

Basically it's a start, but it falls short of what's needed. Since you end up needing to write a bunch of JS anyway you're mostly just creating more work for yourself rather than being able to avoid JS in the first place.

That said, by accident it's also created something close to a universal bytecode since a very wide variety of languages support compiling to WebAssembly.