4 ms·
It's not your imagination, the 1.0 version of the spec was/is widely referred to as MVP - "Minimum Viable Product" - and it was an ordeal just getting that acro
by kevingadd 4y ago
It's not your imagination, the 1.0 version of the spec was/is widely referred to as MVP - "Minimum Viable Product" - and it was an ordeal just getting that across the finish line. It's why so many things are missing. The rest of the ecosystem naturally inherited that state of readiness.
EDIT: I have to disagree though - emscripten is actively maintained. Not sure why you get the impression otherwise.
- deleted 4y ago[deleted]
- hardwaregeek 4y agoMultiple people in the Rust forum explaining that the wasm32-unknown-emscripten backend is unmaintained and broken: https://users.rust-lang.org/t/emitting-es6-module-for-wasm32-unknown-emscripten/84684/3 https://users.rust-lang.org/t/emitting-es6-module-for-wasm32...
- kevingadd 4y agoWe're using emscripten in production right now. New stuff is committed to its github repository every week and there are new releases. I think you're confusing "wasm32-unknown-emscripten" for "emscripten", the latter is a product you can use to compile software.
- hardwaregeek 4y agoI was talking in the context of Rust backends, in which case emscripten is effectively not maintained. I am aware that emscripten is a product you can use to compile software. Frankly that's a little condescending to phrase it in such a way.