@newt @m0xee WASM should be nuked and deleted from Earth, among every single person that contributed to it.

@captainepoch @m0xee WASM as a virtual machine is... fine? Somewhat better than JVM, if you ask me. The problem is the W part, honestly. Documents were never supposed to be Turing-complete.

@captainepoch @m0xee also lol

>In 2022, the startup company named Zaplib summarized in a blog why they were shutting down.[76] Their goal had been to significantly increase the performance of existing web apps by incrementally porting them to Rust/Wasm. However, porting a customer's simulator from JavaScript only yielded a 5% improvement.

lmao even

Ableton (for writing) + Studio One (mixing and mastering). This is the way.

@Humpleupagus @m0xee @captainepoch notepad with staves and pen for writing

@newt @captainepoch
> Somewhat better than JVM
In turn, that one was better than ActiveX.
Yep, often the case: the only justification for using some modern broken shit is that it's slightly better than old horribly broken shit 😂

@m0xee @captainepoch
>ActiveX

i still think you're at least 50

@newt
Why? I didn't have to use it or develop software using it to remember of its existence — and in the corporate space it was still pretty much alive in the early 2000s.
I do remember when MS decided to distance from Sun and made their own incompatible version of Java though 😂

@captainepoch

@newt
I still have no idea what the true nature of the problem was, the standard library was a bit different (?), but when the error came up I had no idea how to fix that and I had to contact colleagues from the head IT office in another country — they've told me to try the *other* Java, surprisingly it did work and I was like: "Wait… WHAT?!!!" 🤣

@captainepoch