How did we get here?
- Traditional distros didn't really provide a way to "work on" development libraries
- Language-specific tools like virtualenv, npm, etc exploded
- Combining these things became so difficult that binary black box solutions like Docker, Flathub, etc took off
- Web 2.0 happened, lots of software *using* FOSS became aimed at *not for end users*
This is *one half* of what has really resulted in a lot of "the developer knows best" kind of mindset which cuts out the user.
Part of why I advocate Guix so hard.
@cwebber I’m of two minds on this. On the one hand, I do like software that treats the user as a participant in the experience, rather than just a passive vessel. I want more of that.
On the other hand, as someone who has had to do both tech support and UI design, user theming can make both those jobs anywhere from much harder to downright impossible. There’s just no way to know where elements are, what they look like, how they relate to each other visually/spatially, etc., if all that stuff can be changed by the user. So by supporting the user in that one way, you take away the ability to support them in other ways.
It’s a hard problem, and I don’t know what the ideal answer is. But if a developer asked me, and they had the power to just disable theming, I would probably tell them to turn it off unless they had a really good, thoroughly thought-out reason not to.
Allowing theming while knowing it can break your app seems like the worst of both worlds. (imho, of course)
@civodul @cwebber Firefox even still lets you customize its own UI via CSS -- a remnant from the days when the whole interface was defined with XML + CSS. http://kb.mozillazine.org/index.php?title=UserChrome.css&printable=yes
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!