Also, considering how simple EVs are: Batteries -> Controller -> Motor -> (Gearbox, optional ->) Differential -> Wheels
I mean, Watch KiwiEV's buildlog videos on youtube - A guy with no mechanical experience whatsoever takes an ICE car and converts it to electric in his spare time.
Clean(er) coal is still mostly an idea, not yet commercially implemented (at least when talking about carbon sequestration in the US).
There's one pretty close to you that is up and running right now, though.
This DMCA takedown request is invalid. And it all comes down to the statement "As the Minecraft Server software is included in CraftBukkit, and the original code has not been provided or its use authorized, this is a violation of my copyright". That statement is incorrect. It is a violation of MOJANG's copyright (As they are the copyright holders of the original server software, which has been decompiled and partially deobfuscated in this case). Wolfe's contributions are licensed under the GPL, and he can't withdraw that license, so he is in no situation to order a takedown on his own code. And he can't order a takedown based on Mojang's code, as he doesn't own that copyright either.
The "Parts of Minecraft" are decompiled and unobfuscated by a third party from the Java binary that Mojang distribute. These parts infringe on Mojang's copyright, and have never been licensed for use anywhere. Technically, Mojang were doing the community a favour by not issuing legal challenges and takedowns for this illegal decompilation of their work.
Oh, and unless I've missed something, Wolfe can't issue a DMCA for his own code, as he has already licensed it under the GPL, and is not allowed to withdraw that license.
1. ok, so it needs a bit of rework to multithread its process-starting system. I that significantly more difficult that rewriting the entire loader?
It needs more than just "a bit of rework", it requires a complete overhaul. Which is what SystemD is.
2. So it needs an extension to monitor services. Technically, I think this is better handled by a different task, one that is more into monitoring rather than blindly just continually-restarting a service that's crashed due to some external dependancy failure. Again, its not much of a task to add this than it is to rewrite the entire loader.
So, instead of one system handling bringing up a service, you want two. One to bring it up at runtime, and another to bring it back up if/when it crashes.
What SystemD is doing is, rather than using a stupid-simple for loop to start things, it's using an event-based system. This also means you can have things happen like "Network comes up, start network-dependent services", "USB printer plugged in, start print daemon", "Device hot-plugged, start dependent services". These are all things that are missing from the current SysV system, and require extra tools, along with their associated extra configuration and extra points of failure.
You're posting a lot on the drawbacks of SystemD, but you're not including any of the drawbacks for SystemV.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (9) Dammit, little-endian systems *are* more consistent!