@ashirsc@rough__sea We don't need DOM in Wasm. We need to start sending a super compact JS engine + DOM lib over the wire with our apps so one day we can get rid of the heavy engines/renderers shipping with browsers.
Instead of a full rewrite, the smoothest way to bring Rust into Node.js could be merging Deno — just like the Node.js + io.js reunion in 2015.
Deno is already mature, Rust-based, has strong Node compat (Deno 2+), and modern defaults. Keep the ecosystem, gradually shift hot paths to Rust, avoid duplicated effort.
Viable idea? @matteocollina
Bun rewrote itself from Zig to Rust.
AI did most of the work.
98% of the test suite passed on the first run.
The question isn't hypothetical anymore. Should we rewrite Node.js in Rust?
Every time software gets better, someone panics that we are forgetting the 'real' work'.
1950s (The Hardware Era): 'Don't forget how to manually patch cables on plugboards and toggle front-panel switches just because we have these fancy new "stored-program" computers now!'
1950s (The Assembler Era): 'Don't forget how to write raw binary machine code numbers just because mnemonic Assembly language does the typing for you!'
1970s (The Compiled Era): 'Don't forget how to write Assembly and manage CPU registers manually just because higher-level languages like C exist!'
1990s (The Managed/Interpreted Era): 'Don't forget how to do manual memory allocation in C just because garbage-collected languages like Java, JavaScript, and Python do it for you!' (Hilariously overnight, C went from being the ultimate 'high-level language' to being treated like low-level assembly).
2010s (The Cloud/Framework Era): 'Don't forget how to write raw SQL queries or configure physical server hardware just because ORMs and AWS exist!'
2020s (The AI Era): 'Don't forget how to manually type out syntax loops just because AI assistants can generate the boilerplate for you!'
Abstraction is literally the history of computer science.
With all the AI usage, no matter how much you try to spec everything out, review and test, you still don’t use your brain in the same way as writing code.
Do you find yourself losing some of your skillset? Here is my experience
https://t.co/kwlCQxu4UF
@samgoodwin89 We need a better syntax for Effect and a compiler for this new language that outputs JS + EffectTS. I think @flowtype has the potential to be that language. It has a powerful compiler, a nice name, and is not afraid to add features to the language. Flow could become the new JS.
@sebastienlorber Hmm google holds on to angular/flutter and didn't make them a foundation. While it sounds nice it also feels like they want to make space for something new.
Jarred experiments with multi-threaded JavaScript 🧪
@filpizlo's "wild thought experiment" is from 2017 is brought to life 🔥
Unlike existing approaches (workers, SharedArrayBuffer) this shares the JS heap. It means threads directly access the same JS objects.