Re: The next generation will attempt to port the kernel to Javascript...
Saying that the next generation will want to use a "not C" language, one NOT intended by its very nature to be the language of OS kernels [think early days of UNIX and the 'B' lingo, which became 'C'], is rather CONDESCENDING in my view. It assumes that future kernel programmers won't be able to comprehend the need for a lingo that's ALREADY very close to the assembly code, and can even be hand-tweeked to generate efficient assembly, if you understand enough about how the compiler works and the way it generates code.
It would also be assuming that assembly isn't being used, assuming that garbage collection and excessive validation are allowable, and that complex operations should be "programmed inside the language" where they're almost GUARANTEED to generate less-than-optimal solutions for MOST problems that require things like threads and process control in general.
We have SEEN the results of "this kind of thinking": WINDOWS
How long does it take to open up a "File Open" dialog box these days? Then go back to Win '95 or even Win 3.1, and that less "functional" file open dialog box that DID! NOT! USE! OBJECT! ORIENTED! HELL! on EVERY! STINKING! FILE! ENTRY! popped up SO fast you're like "what?"
And that's my point: when EVERYTHING is being done using "we have fast CPUs now" as an excuse, with bureaucratic top-down "everything is an object as a member of a collection" kinds of thinking, you end up with GROSS inefficiencies that nobody knows how to fix any more... because we're NOT using a lingo like 'C' any more... one that reminds us of how the CPU actually WORKS, because it's low-level enough to be close to the machine code!!!
[and it has the decency to support "native integer" types, particularly UNSIGNED integers]
Seriously, though, give "the next generation" some credit. We, the experienced kernel programmers of the world, should MENTOR them, and turn them into proficient C coders instead!
[then they'll look back and say "why the HELL dd I ever *FEEL* (the 'F' word) that we could program a kernel in RUST ???]