It sounds like he uses Rust and has some issues with it. IDK about green threads but Ada has had tasks (implemented in gnat with posix threads) from the beginning. If you pin a CPU core to a task and don't use gc in it, that can handle your realtime stuff. Or these days, it's becoming more common to use an fpga for cycle level timing control.

Note that traditional Forth cooperative multitaskers used a few hundred bytes of code or even less. This stuff doesn't have to be bloaty.

Added: I've also seen a Boehm-style conservative GC in a few hundred lines of Forth. Using something like that in Rust could work nicely for lots of things.

Anyway, you can have a soft realtime gc with pauses in the low milliseconds (Erlang has that). That's OOMs lower than most internet ping times, so plenty fast enough for web servers. Which are all full of JS bloat now regardless.

[–] nous 5 points 2 months ago* (last edited 2 months ago)

You could do a lot of things. Rust had a gc and it was removed so they have already explored this area and are very unlikely to do so again unless there is a big need for it that libraries cannot solve. Which I have not seen anyone that actually uses the language a lot see the need for.

Not like how async was talked about - that required a lot if discussion and tests in libraries before it was added to the language. GC does not have anywhere near as many people pushing for it, the only noise I see is people on the outside thinking it would be nice with no details on how it might work in the language.