3 ms·
I think you missed the last paragraph of that comment which also mentions GTK apps applying their own themes, which is still an option. If you know a developer
by lavabiopsy 5y ago
I think you missed the last paragraph of that comment which also mentions GTK apps applying their own themes, which is still an option. If you know a developer who wants to do this then let me know and I can walk them through the process.
I don't understand why you would start reactively uninstalling apps or control would be taken away, I don't believe any of them have gone closed source. If the app is open source then no control can be taken away from you, you can just grab the source and inject your CSS. Again would be happy to walk you through this process, but that would be in the worst case scenario, right now and for the foreseeable future it's unnecessary as you can still use the method I previously described with setting your user theme.
It also doesn't really make sense to me to uninstall some app because of some theoretical bad thing that could happen in the future, if you take that view then you would have to uninstall everything it seems, because there is always a possibility that developers make some decision you don't like 10 years from now when the computing landscape has changed. You can of course stay on an old version if there are some changes you don't like, the developers might grumble more and tell you to upgrade for usability and security reasons, but that's a decision you make according to your own risk factors.
>Flatpak
Huh? Flatpak is an API and CLI, it doesn't use GTK. The ways it's usually accessed through a GUI are GNOME Software and KDE Discover, but you don't have to use those.
- ayushnix 5y ago> It also doesn't really make sense to me to uninstall some app because of some theoretical bad thing that could happen in the future In hindsight, I was perhaps being reactive and might've acted irrationally but I still believe that I should try to stay away from anything related to GNOME or GTK, if possible, simply because I don't trust GNOME/GTK developers to keep their "every preference has a cost" philosophy limited to GNOME itself. Like this, for example. https://gitlab.gnome.org/GNOME/gtk/-/issues/3787 https://gitlab.gnome.org/GNOME/gtk/-/issues/3787 If I'm being polite, pretty interesting comments from Clasen. Subpixel Positioning might make sense on HiDPI displays but most people still don't have them. Yes, that philosophy makes sense in some kind of apps but it isn't one should follow universally, in my opinion. Another simple example is GNOME Screenshot and Spectacle. Spectacle, in my opinion, is perhaps the best screenshot tool on Linux because it offers sensible and basic annotation tools. This is what Android does using its Markup tool on Android and Windows with its Snipping Tool. I suspect Mac has a similar offering. If I want to share a screenshot with some personal information redacted, there's no way to do that using GNOME Screenshot. Yes, I know I can find another app for doing that but that's not the point. It's the "every preference has a cost" philosophy in play again which makes some things dumbed down and deprived of sensible features when they shouldn't be. I am by no means a KDE "fan" though. I ended up uninstalling KDE fairly quickly when I tried it a few months ago. I also stand by my statement of "GNOME not really being a community project" after reading the blog posts by Tobias. There is little room for disagreement besides what the "GNOME way" says and little care for downstream. Thanks for your time though. I appreciate how you've been patiently replying to my comments. Most people I talk to in FOSS communities generally aren't even receptive to discussions when its about disagreement. Everything is either the user's fault or his hardware is faulty.
- lavabiopsy 5y ago>I don't trust GNOME/GTK developers to keep their "every preference has a cost" philosophy limited to GNOME That isn't a philosophy, it's just how development works. Preferences do have a cost, in any project. The actual GNOME philosophy is more along the lines of "GNOME would rather spend the cost of preferences elsewhere" which has been part of the project's philosophy for many years, if you disagree with that decision then feel free to use some other platform. I don't see what your issue is with GNOME Screenshot, you don't have to use it. Just use Spectacle, nobody is going to take issue with you doing that. The builtin GNOME tools are designed to be simple and straightforward, not to include every feature under the sun. Which features an app has is entirely up to its developer, you can say they should or shouldn't do something but it's not your decision to make unless you are developing that app. The developer might listen to community suggestions but they don't have to, and they are very unlikely to if the suggestions are rude. >I also stand by my statement of "GNOME not really being a community project" after reading the blog posts by Tobias. There is little room for disagreement besides what the "GNOME way" says and little care for downstream. This paragraph doesn't make sense to me. The "GNOME way" is just what a group of loosely connected developers all agree on and those blog posts are just one developer's opinion. You're saying it's not a community project but that "GNOME way" is entirely the product of that community, there is nothing else there. Downstream is only relevant as far as they contribute back upstream, because there is no other possible way for there to be any relationship there. But I would say in a lot of cases with FOSS communities, the well has been poisoned and interactions become toxic very fast, I just try to cut that behavior off at the head and correct any misinformation that is out there.