Email or username:

Password:

Forgot your password?
Top-level
Anil Dash

@simon and the other extraordinary thing is it enables the consistency and reliability of environments that’s one of the biggest advantages of the native mobile platforms (or even gaming consoles) without the negatives of the App Store model. There’s just so much potential there.

9 comments
Simon Willison

@anildash absolutely, it really does deliver on Write Once Run Anywhere

🇺🇦 Maksim Lin 💙

@simon @anildash But we already have that with the current Web+JS. What's missing is actually access to all the APIs that only "native" apps via app stores are allowed to use and Apples recalcitrant bevahiour with Safari on iOS is just helping maintain their walled garden.

stephen judkins

@anildash @simon it's one of those things that's not completely original, given that sandboxing and portable bytecode have existed in various guises for me years, so that people are going to bash it as hype-driven or valueless. But it's the combination of features, standardization, and broad adoption that's going to be its selling point

Anil Dash

@stephenjudkins @simon yeah, all of this stuff is the kind of wonderful tech that sort of slowly gestates for a half decade or so, being dismissed as too early, or too familiar, or not “enterprise” enough or whatever. And then suddenly it’s everywhere.

Earthperson Ryan :lvtbq2:‌

@stephenjudkins @anildash @simon I started using WASM for something at work recently and it's freaking wild. I am so ready

Mike Garuccio

@stephenjudkins @anildash @simon this was the refrain about docker too, particularly from the BSD community. But it nailed those three aspects and so adoption skyrocketed whether the haters thought it worthwhile or not. I’m really just becoming aware of wasm, particularly outside the browser, but it certainly feels like it’s got the same energy/momentum.

stephen judkins

@mgaruccio @anildash @simon yes. It was the standard that made it important, not the constituent technologies, which had been in Linux for quite awhile. I'm actually pretty annoyed that docker/OCI was the standard that took off, I think it could have been done a lot differently and better

Mike Garuccio

@stephenjudkins @anildash @simon yea it’s frankly a little weird that underneath all the declarative and immutable tooling that got built on top we have this imperative image build process that gets captured in a tarball with networking and storage defined at runtime.

But, that also made it easy to start using, and flexible for many use-cases. Which really drove the adoption piece of the puzzle (and nature of FOSS meant features followed that adoption)

Go Up