What Happened To WebAssembly

Comments

• user28282912@piefed.social ⁨1⁩ ⁨hour⁩ ago

  It seems to just be more attack surface for very little actual gain on JS. At least with JS I have NoScript, Ublock and some actual say over what loads/runs on my box. For this reason, I usually just disable all wasm/webgl/webrtc until I find out that I actually need it which for me is basically never or only for very short periods.

  source
• AudaciousArmadillo@piefed.blahaj.zone ⁨8⁩ ⁨hours⁩ ago

  For many of these, WebAssembly is critical to either their entire product or a major feature.

  But I think this alone is not very convincing. We don’t yet see major websites entirely built with webassembly-based frameworks.

  Why should it be necessary to build things only in wasm for the web? JS is a really good language for building frontends. There is a reason why lots of companies prefer building native applications with React. People always complain about framework bloat with JS, but then we want to hype up shipping huge wasm binaries? Just for basic interaction in a UI?

  Wasm is doing great, inside and outside the browser. But it won’t replace JS because there’s no reason to do so.

  source

  • MagicShel@lemmy.zip ⁨2⁩ ⁨hours⁩ ago

    I agree with your gist but…

    JS is a really good language for building frontends.

    Disagree. I think there is an entire ecosystem built out of coping with it being an awful language. That being said, the ecosystem is pretty good at adding first class features to a third rate language and your points stand. I don’t want anything to do with JS in the back end, though NodeJS isn’t entirely awful.

    source
• treadful@lemmy.zip ⁨8⁩ ⁨hours⁩ ago

  This makes questions like “how fast is WebAssembly” a bit hard to answer. […] What people actually mean is “how useful are the constructs of this language to efficient mappings of modern hardware” and “what is the current landscape of systems taking advantage of these constructs”.

  Image

  source

  • Catoblepas@piefed.blahaj.zone ⁨8⁩ ⁨hours⁩ ago

    Me after realizing the premise I hinged my entire essay on was faulty and just writing around it instead of starting over

    source
• Nighed@feddit.uk ⁨5⁩ ⁨hours⁩ ago

  I played around for a while with Blazor (C# Web assembly) and wasn’t a massive fan.

  The debugging experience was awful.

  Lots of runtime gotchas, it’s limited to one thread, so anything that creates a thread will fail at runtime (but not ‘normal’ async stuff). What code creates a thread? No idea until it fails at runtime.

  Yes, you can share a dto project between front end and backend, but anything else will eventually trip you up.

  It’s still a cool idea though, will try it again at some point.

  source
• whaleross@lemmy.world ⁨8⁩ ⁨hours⁩ ago

  It is used where it is applicable. For regular web pages it is overkill that only complicates everything with no gain at all.

  source
• theherk@lemmy.world ⁨9⁩ ⁨hours⁩ ago

  Great article. I think wasm is one of the more interesting things to happen in the last few decades in computer science, though there are many. I think it’s here to stay for sure, but am always curious where the adoption curve will go.

  source

  • jungle@lemmy.world ⁨7⁩ ⁨hours⁩ ago

    I don’t know much about wasm, but isn’t it the equivalent of bytecode? That’s just a compiler and an interpreter, how is that a significant development in the last few decades in CS?

    source

    • theherk@lemmy.world ⁨6⁩ ⁨hours⁩ ago

      It isn’t interesting for being bytecode. Rather for being the first universal sandboxes runtime for the browser and elsewhere. Being able to write in many language and compile to wasm targets is awesome. Safety guarantees and performance are both great too. And it can run in tiny environments.

      source

      • -> View More Comments
    • Fiery@lemmy.dbzer0.com ⁨6⁩ ⁨hours⁩ ago

      It’s kinda cool as in you can compile a bunch of languages to wasm, so instead of being locked to JavaScript (/typescript) you can instead code in e.g. rust, have all the advantages of the compiler and still run in the browser.

      source