A different approach to kernel configuration

Some newer systems are arbitrary such as picking a compression or encryption algo at random as 'required' despite the actual code not requiring any single algo, just AT LEAST ONE algo existing from a large set.

Others are setup one-way (the USB <-> networking <-> wireless trifecta for example) for the requirements so if you don't disable things in the correct order you can't disable other things.

And there are numerous "top level items" that could be pushed down a level (or two!) to organize the tree structure in a more 'discoverable' way.

A lot of it is improved Kconfig's being needed IMHO; the existing actual tools are well thought out, but Kconfig's aren't reviewed anywhere near as much as the functional code I feel, so a LOT of really bad cruft and cargo-cult scripting has ended up in those over the years since the syntax seems entirely unique and unrelated to anything else.