sysV is the init system linux distributions used before systemd, openrc, upstart, runit, smf etc. It’s pretty much the old daddy and comes from Linux unix roots. Even MacOS used it before they made their own called launchd.
S6 sounds like a update to it since the capital V in sysv stands for the Roman numeral 5.
Careful with gnome, it works for people that are unfamiliar with gnome, if you use extensions. Then gnome updates, the extensions break and you have to come over do maintenance, maybe use a different extensions which will look slightly different, throwing them off.
And yes I’m talking from experience. It’s bad because there is no easy fix for a broken extension, you essentially have to wait till the author fixes it. It was dock to dash in my example.
For old people you need point and click and the thing they have to click on should be permanently visible. They often do not understand the logical separations with virtual desktops and things showing up on screen only sometimes can be confusing. It’s easier if they have an area that’s always the same.
Nobody is going to rewrite the entire kernel in rust. Parts of it are still written in assembler. It’s well over 30 million lines of code, 60% of it drivers. You can’t just go and rewrite that in a different language, hell it doesn’t even compile on the wrong C compiler version. You would need access to the hardware and run tests for every module you change at least or risk breaking stuff in production.
C programmers will always be around since they are necessary to keep the old code running on newer hardware. There are thousands of companies relying on the Linux and BSD kernels, for example every network router, switch etc.
I have nothing against rust, but there is always a danger of having too many programming languages used in the same project, especially if a error in one language can break something in a module written in the other. That’s just a nasty complication, especially for a time critical project like the kernel.