Yes... let us start with the boot process... good old grub-pc or whatever it's called these days.
Well I have a gaggle of disk drives and each one has it's own independent self sufficient OS on it such that if my computer packs up, I can take a drive out and bolt it in another machine (as long as it has compatible hardware) switch on... and hey-presto there is my OS with all my data that is exactly where I put it on that drive
I can alter the boot priority in the bios and it will boot whatever disk I choose.
It works great with MsDOS, and every windpws ever since... not so much as a single config file to edit!
Alas not so with grub. No... grub being a 'grand unified' omni-everything-system thinks it knows better. update-grub trundles off trashing all my Master Boot Records on every drive it can find and woe betide me if I should remove one of those drives one day for whatever reason.
Now the other day I wanted to change the splash image I get when a Virtual Machine boots... that's so I would be able to recognize the VM I was booting immediately.
It wasn't just a simple config file change... no it took me hours-and-hours of googling and studying documentation that didn't bare any resemblance to the scripts on my installation.
There are default folders with images and things that take precedence over other defaults. IDK how many scripts to run... there is a whole battery of completely unintelligible ones in /etc/grub.d
There are folders full of ghastly 'art' work that I would never dream of downloading given the choice. A file /etc/default/grub that defines some values... but not a single one could I find for the splash image
Eventually I just gave up, I copied the image I wanted to /boot/grub/grubbg.png and I have NO IDEA what all the other files in that folder are for.
So grub is awarded the label 'counter productive bloatware' from me