On Saturday, 7 December 2024 at 17:53:22 UTC, monkyyy wrote:
On Saturday, 7 December 2024 at 15:16:10 UTC, Mike Parker wrote:
He said one thing that had been annoying was that the WASM
interface was basically POSIX, but the compiler didn't treat
it as such for versioning. He'd had to implement a lot of
versioned dummy code to get it to work. He would like to see
the compiler recognize WASM as POSIX.
I imagine he's learned the hard way by now but no, it uses
posix names but its all a lie and you need coordination between
html js and your code to even consider reading a file
"correctly" and I believe all the different places where wasm
can be require slightly different hacks to make it work.
Its probably a bad idea to turn on whatever features as they
will just be broken or worse, pretending to work until you
implement something that actually uses it then youll play wack
a mole for a long time and lets be honest your not going to
find a full time wasm to even attempt to keep up with w3c's
bullshit, much less make it nice and worth using, the least
responsible standards committy on earth may just drop a years
worth of work every 3 months for some rust "feature" no other
language even understands.
Additionally that is now kind of stuck in some political turf, as
the WebAssembly folks are moving into a CORBA/COM kind of
approach with WebAssembly Component Model, and not all parties
agree with this way forward,
https://component-model.bytecodealliance.org/
