Earlier quoted context omitted.
Not a useful question to ask or answer, as the answer is either anything or nothing depending on how nitpicky you want to get or where you feel like drawing an arbitrary line. For example do you consider C++ on Windows to be a proprietary platform, even though C++'s STL isn't proprietary? If so, then WASI on Windows must also be proprietary, no? And if you don't consider C++ to be proprietary, then, you know, you can…
With C++ you have to compile to a specific plattform. So yes, that works, but is different to WASI, where you compile once and can deploy whereever a runtime exists. And apart from that, yes .NET is the only alternative I see today. But you don't see the benefits, of a new lower level option, entering the field?
In a world where CI servers are plentiful, does this actually matter in the slightest?
And aren't you going to end up doing multiple compiles with WASI anyway since the list of required modules for a platform isn't mandatory?
And even if you only use wasi-core, you're still going to be doing platform-specific builds for either the installer to fetch the required runtime or a fat binary that just bundles it. Most likely the latter, like Electron does.
> But you don't see the benefits, of a new lower level option, entering the field?
Not unless it does something new or acknowledges why previous attempts didn't succeed and how this one will be different.
Plans on doing all the same things but years later and with worse tooling isn't exactly a compelling story for why anyone should touch it.