2/9/2026 at 4:00:50 PM
Oh hey, we've reached the "Metal" stage! https://www.destroyallsoftware.com/talks/the-birth-and-death...by fnimick
2/9/2026 at 4:05:17 PM
I'm doing my part ∠(‘-‘)by monax
2/9/2026 at 4:15:15 PM
thank u 4 ur servesby ruined
2/9/2026 at 11:57:38 PM
Interesting to see how many things Gary got wrong.by arxpoetica
2/10/2026 at 1:19:51 AM
Funny, I've always found it interesting how "on point" it was...Granted, yeah, we never (or haven't yet) really transitioned to running "full legacy software" inside the browser, or at least it's not common place. That said, I've seen people compile Wine to wasm, Linux to wasm, and lots of other things to wasm, and run em in a browser. Many of the "fake" demos could be done for real now.
The one aspect that remains thoroughly farcical is an equivalent of Wine for OS X/Cocoa good enough to run a web browser. :-(
[edit] And asm.js kind of died on the vine. Not sure how to feel about that one. Wasm could he described as an evolution of the same idea, but in a lot of ways it's something entirely different.
by spijdar
2/10/2026 at 4:19:22 AM
We already can execute DOS / Win 3.1 in QEMU in the browser.Probably wouldn’t be too hard to boot Linux (under QEMU compiled for wasm), and then fire up a Windows 95 VM using QEMU TCG …
Could repeat this a few times - Inception style…
by BobbyTables2
2/10/2026 at 8:57:41 AM
Go ahead, knock yourself out.by bombela
2/10/2026 at 9:54:08 AM
yep, and 528491 as a password for everything :)by bpavuk
2/10/2026 at 2:53:03 AM
Electronby paulddraper
2/9/2026 at 8:48:23 PM
I don't know if it's only me, but did this guy... Did this guy make a huge mistake?I think he was trying to bend reality with words. I can see many apps that are running in electron on my laptop, each consuming 300MB+ (e.g. Spotify), while many other apps are written in native Swift for example, especially with the help of AI, giving the best performance possible...
Edit.
And prices of RAM nowadays...
by p0w3n3d
2/9/2026 at 8:56:49 PM
Those apps are not consuming 300MB of RAM because they are written in JS. JS is running on microcontrollers and the James Webb Space Telescope.They are consuming 300MB of RAM because they are built on Electron and the NPM ecosystem.
by pwdisswordfishy
2/10/2026 at 4:56:43 PM
Wait a second, JS in James Webb Space Telescope?? Doing what? I'd love to hear about its usecases in the telescope. Is there any blog post about it?by just_testing
2/10/2026 at 11:23:11 AM
There is a pretty significant difference between the way JS is used there and in electron apps.This might be what you were getting to but I tend to agree with the idea of place all the interaction logic in a high kevel language and get the performance where it's needed.
Electron does not do that and neither does the people developing electron apps most of the time. I doubt many people throwing electron apps together chose to do that so they can put their CPU intensive code in C/C++/Rust/swift, they want to erite everything in JS.
What should happen is the bare minimum needs to be in JS and the rest in an efficient compiled language.
I mean even the browser does that, the DOM API hands off to lower level libraries for multimedia etc.
by jpc0
2/9/2026 at 4:20:16 PM
Thank you for the reminder to do my yearly viewing of that video lolby kiddico
2/9/2026 at 5:32:42 PM
Whoa, I haven not been following ASM.js stuff in any detail.Seeing that Metal replaces kernel/userspace boundaries with VM protections for memory, meaning that system call overhead is eliminated, at the price of ASM/VM overhead.
What a fascinating idea. Kidding on the square...
by epistasis