4 comments

  • simonw1 hour ago
    I&#x27;m unreasonably excited about WASI. WASI is the thing which takes WebAssembly from a tool for running stuff in a browser to a tool that can run entire portable sandboxed applications on a computer - with controlled filesystem and network access.<p>I don&#x27;t ever want to run untrusted code from the internet outside of a sandbox ever again. If WASI lives up to its full potential I won&#x27;t have to - we&#x27;ll have a robust, cross-platform sandboxing solution for running real applications.
  • thefounder59 minutes ago
    It’s great we are past the “wasm is not replacing JavaScript” phase. Or “you don’t need DOM for wasm . That’s what JavaScript is for”
  • fyrn_1 hour ago
    Please please please bring it to the browser. I&#x27;m so done with the terrible ergonomics of everything at the was bounary having to pretend it&#x27;s JavaScript
    • enos_feedler24 minutes ago
      It works in the browser already: <a href="https:&#x2F;&#x2F;github.com&#x2F;bytecodealliance&#x2F;jco" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;bytecodealliance&#x2F;jco</a>
      • jauntywundrkind3 minutes ago
        It works in the browser already, <i>by bundling another browser runtime engine into wasm.</i> You need a whole fork of Mozilla&#x27;s SpiderMonkey engine, compiled to wasm, running in whatever browser you have, to run wasm components today.<p>I confess I was quite frustrated at first when browsers all said no to wasi &#x2F; wasm components. But honestly, it was the right call. It&#x27;s taken so long to make wasm components happen, to get them far enough along to start really consider implementing. I can accept that as just the reality of what it takes for a small team to do such amazing work. I am so thankful for the folks who have kept this going, kept advancing.<p>But it&#x27;s time now. I hope browsers can help get us set up for 1.0, and I hope they&#x27;re moving quickly towards being ready to implement!
  • shevy-java59 minutes ago
    WASM first appeared in 2017.<p>It still hasn&#x27;t really reached a breakthrough.<p>Billions use HTML+CSS+JavaScript. Who really uses WASM? There are of course users, but very, very few in absolute numbers. Many projects are not web-based really. For Autodesk Fusion, as one example for many, I have some mega-slow application that takes forever to work with in some cases on my laptop (it is not the fastest laptop, but I recently tested this on a faster desktop computer with 32GB RAM and it is still slow to no ends; using it all WASM based would be even slower I bet. That&#x27;s not winning anyone over ...).
    • simonw0 minutes ago
      According to <a href="https:&#x2F;&#x2F;chromestatus.com&#x2F;metrics&#x2F;feature&#x2F;timeline&#x2F;popularity&#x2F;4689" rel="nofollow">https:&#x2F;&#x2F;chromestatus.com&#x2F;metrics&#x2F;feature&#x2F;timeline&#x2F;popularity...</a> WebAssembly runs on about 6.11% of Chrome page loads, up from 3.37% in January 2024.
    • h4ch128 minutes ago
      I wrote an Unreal file parser in C# and use it in our in-house web based DAM. It was much more ergonomic and performant than writing it in Javascript.
    • esafak47 minutes ago
      WASM made Figma.
    • aatd8634 minutes ago
      WASM is super useful for FFI in some env