User's banner
Avatar

FOSS Is Fun

fossisfun@lemmy.ml
Joined
0 posts • 52 comments
Direct message

Your’re right, ideally wear reduction should probably be done by the display itself. But considering how little manufacuters often care about OS-agnostic approaches, it might be necessary to have software workarounds?

permalink
report
parent
reply

Variable refresh rate (VRR), HDR, OLED (e. g. I’d like the panel to become grey and move items around a bit to lessen burn-in) all involve GNOME for hardware support.

permalink
report
parent
reply

Outside of that the toolkit’s file picker is used, as the system doesn’t seem to provide one (via the portal), so the only reasonable fallback is to show the file picker that you know is there, which is the one of the application’s toolkit.

permalink
report
parent
reply
4 points

I actually like to use Comic Neue for personal stuff. https://comicneue.com/

Ubuntu is another nice font, which I like to use for more serious documents. https://design.ubuntu.com/font

For system fonts I use whatever comes preinstalled. I don’t modify the font defaults in any way.

permalink
report
reply

but you are writing documentation for scripts?

No, I document my installations with scripts, so that I am able to install multiple computers the same way.

permalink
report
parent
reply

how would that impact your configuration?

It impacts my documentation. If, for example, gsettings set org.gnome.software allow-update false no longer works, because they changed the key from allow-update to updates-allowed, then my documentation no longer works correctly. Same when new technology is introduced, e. g. a switch from Pulseaudio to Pipewire. With a rolling release distribution these changes can happen at any time, whereas with a fixed release these changes only occur when a new release of the distribution is made and I upgrade to it.

I don’t have the time to continously track these changes and modify my documentation accordingly. Therefore I appreciate it if people bundle all those changes for me into one single distribution upgrade and write release notes with a changelog. Then I can spend a day reading the release notes, adjust the documentation, apply the upgrade on all devices and then move on for the next couple of months/years.

which as nothing to do with rolling release or distributions.

I tried to explain to you why I dislike rolling release distributions. That’s why I tried to give you one example where a fixed release distribution is more suitable in my opinion.

I understand that these things might not matter to you, if you only have one computer (or so) to maintain at home or maintaining home computers is your hobby. But I have four personal computers and multiple devices from the family to maintain and system administration is no longer my hobby …

permalink
report
parent
reply

I’ve used Arch Linux and openSUSE Tumbleweed in the past and I have been using Linux for over 10 years …

With each new version of an application there’s the change that configuration files or functionality changes. Packages might even get replaced with others.

You would be surprised how much changes between Ubuntu LTS versions … My archived Ubuntu installation script had lots of if-statements for different versions of Ubuntu, since stuff got moved around. Such things can be as simple as gsettings schemas (keys might get renamed), but even these minor changes make documentation and therefore reproducable reinstallations troublesome.

With a fixed release all these changes are nicely bundled in one large upgrade every couple of months/years, which makes it easy to document and to plan when to do the upgrade.

permalink
report
parent
reply

I can’t stand rolling releases (for personal use) and I never recommend them to anyone. To me it feels like being in drift sand.

I need fixed releases to test my documentation (shell scripts) against something. With a rolling release those scripts can break at any time, unless you read the changelog of every package update.

But I also want and use fully automatic updates, so reading changelogs for every update would be the direct opposite of what I am looking for in an OS. I am ok with reading release notes every couple of months for a distribution upgrade though.

I want my systems to be reproducible and that’s impossible with drift sand rolling releases. In my opinion Fedora or Ubuntu have a decent release cycle, I would never consider Arch or Tumbleweed or Solus.

permalink
report
parent
reply

Innovation or regression?

Innovation doesn’t necessarily mean that all past functionality needs to be carried over. Actually innovation often means that past technology becomes obsolete and gets replaced with something new.

Gnome used to have optional desktop icons. They removed them.

They removed them because with GNOME Shell those icons no longer made sense. There was no longer a concept of dragging apps from a panel menu to a desktop, instead apps were now pinned from the fullscreen app overview to the dash.

Since the code was no longer used by the default GNOME experience, it became unmaintained and eventually got removed.

permalink
report
parent
reply

Because GNOME is the only DE with some potential and by not having 2 or 3 simple optional features aren’t getting more traction.

But everyone has different requirements and my “2 or 3 simple optional features” that are missing are completely different than what you think is missing. I couldn’t care less about desktop icons or system trays. I even prefer not having a system tray, as this functionality should be provided via notifications and regular application shortcuts in my opinion.

But in the end, a software project only has a limited amount of resources available and developers have to decide where they want to focus on. GNOME chose not to focus on desktop icons:

GNOME had icons, v3.28 discontinued them

Because the code was “old and unmaintained” and probably no one was willing to modernise and maintain it. Desktop icons were already disabled by default before 3.28, so they didn’t “re-invent” this feature with the removal of the code in Nautilus.

Using other DE doesn’t make much sense as you’ll inevitable run in GTK and parts of GNOME and having to mix and match to get a working desktop experience.

I use GNOME and KDE and use the same applications (as Flatpaks) on both desktops: I use GNOME Calculator on KDE, because I dislike both KDE calculators, and I use Ark on GNOME with a Nautilus script, as File Roller doesn’t allow me to set the compression ratio (I need to create zip files with 0 compression for modding games). So for me it has become the norm to mix applications created with different toolkits. Thanks to Flatpak I still have a “clean” base system though.

Btw. I am getting tired of these re-occurring complaints that GNOME works differently than other desktops. I am not constantly complaining about what features KDE is, in my opinion, missing all the time either (e. g. dynamic workspaces, same wallpaper and desktop configuration across all existing and new monitors, online account integration, command line config tool, etc.), instead I accept that this is how it is at the moment and either use KDE the way it is (like I do on my desktop PC) or use something that better suits my needs (like I do on all my laptops).

permalink
report
parent
reply