3 ms·
That's cool, but you can't run standards. I tried Mono since its early days and kept trying until .NET Core came, but it was nowhere near production-ready, it w
by butthatsit 4y ago
That's cool, but you can't run standards. I tried Mono since its early days and kept trying until .NET Core came, but it was nowhere near production-ready, it wasn't enough for my school assignments, much less production.
I'm not saying it changes anything. Wasm is just a more modern attempt, like .NET itself. I don't see any reason to prefer one or the other only because of its age.
- pjmlp 4y agoThose school assignments would have been sorted out by using Windows in first place. It is not like all those beautiful WASM implementations support the same set of features, from the paper standard, https://webassembly.org/roadmap/ https://webassembly.org/roadmap/
- butthatsit 4y agoWell, I wanted to use Linux, not Windows. And my servers ran (and still run) Linux, not Windows. The point wasn't that I couldn't do my school assignments (I was forced to use Windows VM) but that not even this simple task could be accomplished - so running it in production was straight up impossible. Wasm is much newer than Mono was at the time. Let's wait.