Open Source on its own doesn't mean the average user can make choices with a reasonable effort. A big thing for me in any desktop environment is, can I (1) hav

Open Source on its own doesn't mean the average user can make choices with a reasonable effort. A big thing for me in any desktop environment is, can I (1) have the focused window stand out from others - for example a colored title bar, and (2) choose my own accent color? There was a time when this was no problem - Windows 3.1 could do it, so could Windows 95, and pretty much any linux distro before "the one theme to bind them all". There was a setting for this in a dialog box in most cases, but even if you wanted to experiment with some new theme, since it was all bitmaps and palettes the worst you'd have to do is edit a config file and change GTK_COLOR once or so. Nowadays, the closest I can get on the "modern" branches of things is regexp-replacing hundreds of lines of CSS, unless I want to build the themes part from source and spin up a whole dev environment to do it. Open Source doesn't help one bit - the difference for me is between 1 minute changing a setting in a dialog box, or half a day trying to understand how the system works because what I want to do clearly wasn't intended. Or consider chromium. It's open source, right? So I could in theory fix the problem that manifest v3 will no longer play nice with the full ublock origin myself? Yeah, right. What makes it so easy on v2 is not that chromium is open source, but that it offers a plugin interface and API so that people like gorhill can write extensions like ublock, and people like me can just click and install them. The only code I then have to write is then things like `##.featured-video`.