That site isn’t RedHat/GNOME. From the bottom of the letter:
Note: Even though some of us are Foundation members or work on GNOME, these are our personal views as individuals, and not those of the GNOME Project, the GNOME Foundation, or our employers.
They aren’t against user theming. Again, from the site:
If you like to tinker with your own system, that’s fine with us. However, if you change things like stylesheets and icons, you should be aware that you’re in unsupported territory. Any issues you encounter should be reported to the theme developer, not the app developer.
They’re against distributions shipping custom stylesheets by default. Which makes sense! If a user has a stock installation, and an app looks broken, they aren’t going to assume the distribution messed it up. They might not even know that the distribution changed the theme. It can also cause confusion for users when their app doesn’t look like the screenshots from the developer. These cause issues for app developers.
That’s it. That’s all the letter is saying. It’s not a crusade against you theming, it’s asking for theming not to be done by distributions.
(P.S. I don’t intend for this to be aggressive. Just wanted to explain a bit more, because the name does sound… not great.)
Yes, but only for apps that which I want to be on the very latest versions. One might ask why I don’t use a rolling release distro, that’s because I prefer a solid LTS base.
I usually use the terminal, so that is something I need to make sure of. Otherwise, using the Software Store I can explicitly choose which version to use.
I want to be on the latest Firefox and to have the latest LibreOffice and some other apps. I want the latest applications, but I don’t want them come at the expense of having my system randomly lose its Wifi at the next boot or some other trash.
FreeBSD had this figured out 25 years ago. Separate the base from the user apps. When I was a teenager, I built -current ports on top of -stable FreeBSD and it was fine.
Now we have the equivalent option in Linux, and it comes from a centrally managed repository i.e. I’m not downloading tarballs and managing my own packages. I’m too old for that crap.
First Linux servers I installed were RedHat 4.2. I stick with RH until 8.0. Then they stabbed us all in the back, starting to charge for it.
Have you RH users been fooled twice?
I switched to the then (and still?) distro that was most strict in commitment to FOSS - heck, they forked FireFox just because of the logo copyrights - Debian.
(RH to kubunto at home, because Debian then was (is?) too “enterprise” for home, and I wanted to stick to the same packaging)
The only other distro I’ve been using is SUSE (SLES), because that’s what SAP suports for HANA database servers.
SUSE should gradually morph the RH fork into becoming SLES, and always provide an easy automated way to migrate, a one way only route to leave RH.
I like the quotes she put up on the screen about Canonical and System76.
I’ve kept coming back to Ubuntu over the years, but ultimately, they are a corporation, and they need to satisfy their shareholders. Someday they will likely be bought out, then who knows?
Some apps automatically pick up your theme some don’t. For these I give the specific app access to my theme folder with a :ro at the end of the path.
IDEs should work ootb. If some extension doesn’t work, maybe it’s because of poor support for Flatpak. 9/10 times you’ll find the issue is that app is calling the traditional /usr/bin path etc. when Flatpak installations use different paths.
Appimages are nice. I just would like there to be some hub for them which also enables the appimages to be updated through it. I know about zap for example but it’s not up to par with flathub or the snap store.
Flatpaks (and Snaps, and Appimages and Docker containers for that matter) are essentially designed for app developers who grew tired of distro maintainers demands to fix certain things about their build systems and their applications that broke when their apps were used on distros other than the exact distro and version the developer was using. They are designed to take a “kill the messenger” approach to the problem and now people are wondering why the work that the distro maintainers did before doesn’t get done any more.
I have enough money to buy a more modern Lenovo laptop, but I’m definitely considering getting one renewed simply because of how cheap it is. I’d prefer newer age specs tho. Thank you!
I also had one and not because of any money restriction. It’s just an amazing machine with a few tweaks and the CPU limitation are actually a plus since it will push you towards cli/tui and that’s where the fun begins
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.