2 ms·

> Because the "MVP" stage is itself production ready > some non-MVP features are almost stable > the posix-like system interface ABI, is still technically a "

> Because the "MVP" stage is itself production ready > some non-MVP features are almost stable > the posix-like system interface ABI, is still technically a "snapshot" So... It's not production ready.

kthxb 6y ago
WebAssembly's MVP release was primarily targeted at the ... web. It is production ready in all (vital) aspects concerning execution in a browser.
- dmitriid 6y ago
  > It is production ready in all (vital) aspects concerning execution in a browser As in (emphasis mine): "This means that there are important features we know we want and need, but are post-MVP" [1] As in: "a Minimum Viable Product (MVP) for the standard with roughly the same functionality as asm.js, primarily aimed at C/C++;" It's good that you specified "vital" when talking about "all" aspects. Where vital is basically "let's run MVP in an isolated sandbox with little-to-no interoperability with the rest of the browser". Because the rest of the vital things like "basically everything" [3] [4] are still MIA. But yeah, I mean, the modern web was built on a language designed in 10 days, so I shouldn't complain, should I. [1] https://github.com/WebAssembly/design/blob/master/MVP.md https://github.com/WebAssembly/design/blob/master/MVP.md [2] https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md https://github.com/WebAssembly/design/blob/master/HighLevelG... [3] https://github.com/WebAssembly/design/blob/master/FutureFeatures.md https://github.com/WebAssembly/design/blob/master/FutureFeat... [4] https://github.com/WebAssembly/proposals https://github.com/WebAssembly/proposals
cortesoft 6y ago
'Production ready' doesn't mean it has all the features you would ever want. It means it is stable and tested enough to run critical workloads. They are saying the core is production ready (if your needs are met by the features included in the MVP), but that planned additional features are not yet production ready.

kthxb 6y ago

WebAssembly's MVP release was primarily targeted at the ... web. It is production ready in all (vital) aspects concerning execution in a browser.

dmitriid 6y ago
> It is production ready in all (vital) aspects concerning execution in a browser As in (emphasis mine): "This means that there are important features we know we want and need, but are post-MVP" [1] As in: "a Minimum Viable Product (MVP) for the standard with roughly the same functionality as asm.js, primarily aimed at C/C++;" It's good that you specified "vital" when talking about "all" aspects. Where vital is basically "let's run MVP in an isolated sandbox with little-to-no interoperability with the rest of the browser". Because the rest of the vital things like "basically everything" [3] [4] are still MIA. But yeah, I mean, the modern web was built on a language designed in 10 days, so I shouldn't complain, should I. [1] https://github.com/WebAssembly/design/blob/master/MVP.md https://github.com/WebAssembly/design/blob/master/MVP.md [2] https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md https://github.com/WebAssembly/design/blob/master/HighLevelG... [3] https://github.com/WebAssembly/design/blob/master/FutureFeatures.md https://github.com/WebAssembly/design/blob/master/FutureFeat... [4] https://github.com/WebAssembly/proposals https://github.com/WebAssembly/proposals

cortesoft 6y ago

'Production ready' doesn't mean it has all the features you would ever want. It means it is stable and tested enough to run critical workloads. They are saying the core is production ready (if your needs are met by the features included in the MVP), but that planned additional features are not yet production ready.