We need to fork the kernel to purge the sloppers from the project.

Yeah but I'm going to keep saying it until somebody actually does it, that way somebody has the opportunity to fill me in on the development.

Unfortunately, at this point it's effectively impossible to fork the kernel, there's enough churn that any fork will very quickly go out of sync, and also the sheer amount of commercial backing Linux has won't move over to a community oriented fork.

Any actual successful fork you'd see, is e.g. Google forking Android off entirely and stop contributing back upstream.

There are a lot of Kernel Forks, and some Linux have instructions on installing them such as CachyOS. What we're missing is an Anti-AI Kernal, afaik.

I dont know if I'd call them forks, they're more like unmerged branches.

Like the bulds with different schedulers, the only thing different about them is they include an extra module that's not included by upstream, everything else is a 1:1 match for upstream, and follows closely.

I'd personally say the real-time kernel would come close to it, but even that was still roughly tracking upstream, and was merged in the end.

I think the point is that they have different maintainers. Of course removing and preventing slop code and unattributed code is essential as well, but that's secondary.

I'm still waiting on the fork where they don't use electricity, because anything made with electricity is slop.