Little more philosophical with less practical examples, and a bit ranty, comment incoming: Linux did not proactively foster standards on anything beyond the ke

Little more philosophical with less practical examples, and a bit ranty, comment incoming: Linux did not proactively foster standards on anything beyond the kernel. Sure many would shout "not their job!" but here we are in 2022, every disagreement in an obscure chat channel or a forum only 500 people on the planet know exists leads to a new distro, or a fork of a high-profile library, or yet another pre-built KDE/GNOME configuration claiming usability / accessibility and whatnot. Fragmentation abounds, egos are flying around. Feels like a kids club arguing with another kids club about which Transformer toys are the coolest. Like, come on already. Agree on a common goal and start pursuing it. Moderate aggressively -- if somebody is being a dickhead just boot them out. Done. (Would have saved at least 17 people no less than 10 hours each, judging by several random encounters I witnessed some years ago.) --- Non-exhaustive list: - We need strong schema for cooperation between tools. A tool like `jc` that strives to parse various UNIX tools outputs and convert them to JSON shouldn't even exist yet I find it indispensable for most of my throwaway scripting or homegrown data-science needs. - We need less copying between user space and kernel space. - We need to start moving away from "everyting is a file" and have some standardized SQL-like interface to the OS (or any other query language that makes sense for the task; people will adapt). - We need less Python scripts being responsible for, well, almost everything. It's collectively embarrassing and makes a ton of distros very brittle (upgrade from 2.7.X to 2.7.Y and hilarity ensues). - We need to start bundling more things into the OS by default. People love standards and that's the (apparently inconvenient) truth. Endlessly parroting "freedom!" has gotten us nowhere as it's very clearly visible by the state of anything non-kernel related in Linux land. --- A lot of things from the 70s and 80s still make sense today. But some no longer do and we should recognize that and start moving forward because that old way of doing things is actively hampering progress of the entire IT area. And no I truly don't care if I get automated out of my job as a result. At one point the area has to progress further. We are in an evolutionary cul-de-sac. --- It really does seem that non-kernel Linux work is mostly picked up by very immature people who don't seem to be professional programmers at all.