• fonix232@fedia.io
    link
    fedilink
    arrow-up
    3
    ·
    19 hours ago

    See the main issue with that is you need to bundle everything into the app.

    Modern computing is inherently cross-dependent on runtimes and shared libraries and whatnot, to save space. Why bundle the same 300MB runtime into five different apps when you can download it once and share it between the apps? Or even better, have a newer, backwards compatible version of the runtime installed and still be able to share it between apps.

    With WASM you’re looking at bundling every single dependency, every single runtime, framework and whatnot, in the final binary. Which is fine for one-off small things, but when everything is built that way, you’re sacrificing tons of storage and bandwidth unnecessarily.

    • gandalf_der_12te@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      9 hours ago

      With WASM you’re looking at bundling every single dependency, every single runtime, framework and whatnot, in the final binary.

      you just don’t know what you’re talking about. wasm has a module-import structure with which you can link libraries at program start-up, and some wasm runtimes also offer possibilities for linking libraries at run-time.

      • fonix232@fedia.io
        link
        fedilink
        arrow-up
        2
        ·
        8 hours ago

        Oh, good to know. Last time I checked around WASM this wasn’t really an option.