if you get into a config system that's complicated enough, and has modularization or inheritance, you'll know that the semantics of "remove this" "add that", override this, default to this, this stuff is hard to express in most config languages, or worse, you start enforcing application level semantics. when you have turing complete language you just ... do those things. we reduced the configuration data of a tool suite once by 90%+ by moving from json to python. there was a tremendous amount of duplication and overlap, with tons of TINY exceptions and variations. it was so hard to see those differences, brittle to maintain, things would get stale, ... moving to python you basically had the "base" thing expressed in one file, and a bunch of tiny delta files encoding the exact deviations. All those deviations were of the forms I described above. Adding a thing to a list. Removing a thign from a list. Overriding a whole list. Do a thing if not already done. And so on. It's also then easy to build all kinds of diagnostics, validators, etc, right into the same framework, without having to munge the data into some other form first.
Google is historically terrible as a product company (and has succeeded in spite of that) As their technical innovations become less of a moat (we're already there) they won't be able to win on engineering alone (they are no longer winning on engineering alone)
Having "accidentally" purchased one, I can tell you that doing anything 8GB or RAM on a mac laptop is impossible. I have no idea what people are doing with this laptop. Macs are absolute dogs at 8GB.
The engineer who only does high level system design and never codes has existed for decades and is often the most useless and derided engineer in the org.