

The part that bothers me the most about this is how the re-institution of child labor points to the damnable confusion of moral, ethical, and legal, activity. Clearly this isn’t moral or ethical, but it is legal. So, undoubtedly some will point at the law and reassure themselves and others that this alone makes it okay to do. While there’s no stopping people that lack moral fiber to do the right thing, it’s everyone else that decides on the wrong side of moral and ethical conflict that make this so much worse.
On another note: how does one effectively boycott this behavior? No doubt, a lot of this labor will happen sight-unseen.
I agree and disagree.
The premise is solid: unify config so it’s standardized and machine parse-able for better integrations like an easier-to-build UI/UX. It could even have ramifications for cloud-init and older IaC tech like Puppet.
The problem is Linux itself. Or rather, the subsystems that are cobbled together to make Linux a viable OS. You’re not going to get all the different projects to pivot to a common config scheme, so this YAML standard would need a backend to convert to/from whatever each little deamon and driver requires. This creates a few secondary problems like community backlash (see systemd), and having multiple places where config data must be actively synchronized.
I think the current crop of GUI config systems are aleady well down the most pragmatic path: each config panel touches one or more standard config files, wherever they are, and however they are structured. It’s not pretty under the hood, and it’s complicated, but it works. These tools just need a lot more polish on the frontend.