5 ms·

Just like docker image vs specialized language runtime ?

• throwawaymaths 3y ago
  Sure, but for many langs hermetic config is an issue, you want to be relatively sure what your devs are building against is what gets deployed.
  • moonchrome 3y ago
    So you'll develop directly on the wasm runtime locally which should be a platform abstraction ? The way I see it VM -> Containers -> WASM is a logical progression in the same direction from the perspective of deploying applications.
    • deleted 3y ago
      [deleted]
    • throwawaymaths 3y ago
      I mean i don't think you get it. Wasm doesn't ship with a filesystem, POSIX support tools, etc. You only get your language runtime, so they're not comparable. Bare metal, VM, and containers all "look the same", like from a UX perspective. Wasm does not.
      • moonchrome 3y ago
        That's solved by WASI which is like POSIX of WASM. Nobody is arguing that WASM today will replace containers - 2030 is a long time away in tech.
        • throwawaymaths 3y ago
          Wasi is POSIX but not like filesystem, ls, cat, etc.
          • syrusakbary 3y ago
            WASI is not POSIX. WASIX is POSIX :) https://wasix.org https://wasix.org
            • throwawaymaths 3y ago
              I though wasi recently voted to add POSIX in officially