Re:$30M Raised to Redo the CPU
by CyberDildonics on Wednesday November 11, 2026 @10:33AM
(#50454635)
This is a big misunderstanding of languages and multi-threading. First, plenty of languages including C++ have a const keyword, rust is just const by default, so that doesn't enable anything new through the language. Even marking something const doesn't enable anything new, it's just convenient safety.
Single threaded programs being normal was originally from almost no systems having more than one core or CPU. Then there were few languages that had threading built in. Someone knowledgeable would have to use the OS API to launch threads.
After that threading has mostly come from structures that are already built. There is nothing difficult about copying data if that's what people want to do. There is nothing that says scheduling has to be slow since you can have threads taking data from a queue. None of this has anything to do with rust.
you are no longer being slowed down by the software scheduler in the kernel
This isn't necessary if you just create threads and let them grab data they need, work on it and move on.
The other problem is that automatic parallelism with the right language is actually easy, but the scheduling cost eats the gains because you cannot launch subtasks in the 100s of nanoseconds timescale.
What's needed is hardware accelerated scheduling within the same process so that you are no longer being slowed down by the software scheduler in the kernel.