Re:Libc++ 9.0.0 adds explicit support for WASI
by pjmlp on Friday October 11, 2019 @04:41PM
(#21228273)
Which are utterly meaningless with the specification developed by said corporations.
And really, the only thing going for WebAssembly is being the PNaCL that those corporations were willing to agree on.
Re:Libc++ 9.0.0 adds explicit support for WASI
by krapp on Friday October 11, 2019 @05:23PM
(#21228603)
It's not the best possible scenario but "utterly meaningless" is hyperbole.
Certainly it's better not to have every aspect of a language be centralized. It's already near impossible to distribute Javascript, or even software in many languages, without going through NPM. WebAssembly, thankfully, isn't there yet.
Re:Libc++ 9.0.0 adds explicit support for WASI
by pjmlp on Saturday October 12, 2019 @04:06AM
(#21231406)
It surely is meaningless, because whatever your favourite WebAssembly implementation is capable of, ultimately it only matters if it is spec compliant.
A spec, which is under control of those organisations.
Re:Libc++ 9.0.0 adds explicit support for WASI
by iwillrunoutofsp on Saturday October 12, 2019 @06:05AM
(#21231873)
What organisations should control a standard if not those that develop implementations?
Although Wasmer does come with a package manager (WAPM) that uses a proprietary registry like NPM, at least the developers have said they're committed to decentralized hosting[0]. Maybe someone can come up with a completely distributed package management alternative, which I would prefer, but at least Webassembly isn't yet at the degree of centralization that Javascript is.
[0]https://news.ycombinator.com/item?id=19732794