> Wouldn’t it be great if there were a libc in the JS world. Something portable and standardised.
I mean, it’s not necessarily “in the JS world”, but WASM is basically that.
No it’s not. Problem right now is that every WASM files pulls in its own stdlib. Which is a waste once you use more than one.
Re:The Everything NPM Package
by swiftcoder on Sunday January 07, 2024 @02:50AM
(#38899386)
WASM is explicitly not that. WASM itself has no APIs, it's just an execution envionment.
You may be thinking of WASI?
We’ve been blessed in recent years that either languages are fully open source and come with a reference implementation, or a standards body governs the implementation detail. Sometimes even both.
Whereas JavaScript is really more a group of languages, each with their own implementation quirks.
ECMA was intended to bring some sanity to all of this. And it’s definitely better than it was in the JScript days of IE vs Netscape. But there isn’t anything (that I’m aware of) that defines What should be a part of the JavaScript standard library.
Wouldn’t it be great if there were a libc in the JS world. Something portable and standardised.