NodeBB

@a1ba@suya.place @cnlohr@chaos.social I mean, almost everything that isn't JS or Lua or similar is hopelessly tied to POSIX. You either reduce the stuff that's donw in other languages to end up as just simple processing routines, end up implementing emscripten yourself, or rewrite it in JS.

@a1ba@suya.place @cnlohr@chaos.social you understand that you don't have to use emscripten, right? Many don't.

It's just that nobody cares/wants to build websites from wasm alone

@a1ba@suya.place @cnlohr@chaos.social most of wasm's utility was and is in the fact that you can have a way to use existing, non-browser code in browsers

if you want to use wasm instead of JS - just get down for a bit to write the JS wrappers, and congratulations - you can now have a painful experience dealing with browser API's from other languages

@a1ba@suya.place @cnlohr@chaos.social right, but still - the wast, wast majority of software is useless without posix calls

sure, you can provide some interface to web apis, but you'll still often need to wrap libraries/posix to fit into web apis

so in the end you're just moving where you're doing the wrapping

@a1ba@suya.place @cnlohr@chaos.social again, I think it's more of a language interface question (what does DOM API look like in C) than a wasm interface question

@a1ba@suya.place @cnlohr@chaos.social Just like it's useless outside of the browser without other code

I don't see why it should be particularly different in browsers. And this way, there's way more flexibility with it.

@a1ba@suya.place @cnlohr@chaos.social consider - stuff that runs in browsers are applications

@a1ba@suya.place @cnlohr@chaos.social look, I don't disagree than emscripten is shit

I'm just saying that it's not wasm's fault that there's no wrapper for just connecting to browser interfaces

@a1ba@suya.place @cnlohr@chaos.social yeah

what I meant more, is that if you want "wasm with web interfaces" - that's entirely possible to have with a wrapper, it's more of a question from the languages you're compiling to wasm to support it (emscripten is easy because posix has near-universal support, while browser interfaces don't)

@a1ba@suya.place @cnlohr@chaos.social tbh wasm was done in a way where by default it can't do anything, so in general to do anything with it you have to do wrappers

emscripten is just one of those

@a1ba@suya.place good question

I mean, technically the reference decoder is a standard https://www.iso.org/standard/80619.html

"Hey guys, look I created a "reference JPEG XL decoder in rust", hope this helps!"

It's LLM slop that has obviously never, ever decoded an actual image.

Why do people even do this shit. Like sure, whatever, if you really want to, guide an idiot through writing a JPEG XL decoder, but you probably should check if it can even read out the headers correctly.