In my opinion Plasma has gotten much better with the last couple of releases. Around 5.21 the defaults actually got pretty good and since 5.24 Wayland support is quite good, on par with GNOME in my opinion.

After using GNOME Shell for a decade I have recently switched to Plasma 5.27 on my desktop due to its VRR support (I have two 170 Hz QHD monitors). A couple of weeks later I also moved my laptops to Plasma, even though I wanted to keep GNOME on them, since Plasma has gotten so nice!

Just wanted to give a heads-up in case you haven't tried Plasma in the last couple of years. ;) But especially if you rely on dynamic workspaces and don't want to adapt your workflow (like I did when I switched to Plasma), there's just no alternative to GNOME and it has gotten really polished and nice as well.

Linux Mint nowadays supports release upgrades, but you have to follow their blog to know when a new major Mint release is out and you have to manually install mintupgrade and do the upgrade.

So it is definitely not caused by technical constraints, as Mint has implemented the difficult part (providing and testing an upgrade path) already. Notifying the user about a new release upgrade shouldn't be too difficult? E. g. in the most simple form you could probably preinstall a package that does nothing at first, but receives an update once the next Mint release is out to send a notification to the user to inform about a new Mint release.

When it comes to elementary OS, I think they could support in-place upgrades, as they properly use metapackages (unlike Mint, which marks most packages as manually installed and doesn't really utilise automatically installed packages and metapackages in a way that you would expect on a Ubuntu-based distro), but they probably don't want to allocate / don't have the resources to test an official upgrade path.

But again, I don't understand why it is so difficult for elementary OS to at least provide a simple notification to the user that a new version is out. Even if the users have to reinstall, it is critical to inform them that their OS is about to become end of life. You know, people do things like online banking on their computers ...

It's the first thing I check with every distribution and if it doesn't have an EOL / upgrade notification, it is immediately out.

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?

Because it takes manpower to develop and maintain these features?

Especially desktop icons are difficult to get right (see workarounds like "ReIcon" on Windows). E. g. keeping icon positions across multiple monitors and varying resolutions and displays (which can be unplugged at any time). They can also be a privacy-issue, e. g. when doing a presentation.

But most importantly: GNOME doesn't want to be a traditional (Windows-like) desktop, so why would they implement features that don't align with their ideas for a desktop experience?

There are lots of other desktops, like Cinnamon, that offer a traditional desktop experience within the GTK ecosystem. There is also plenty of room for desktops, like GNOME, that have a different philosophy and feature set.

In my opinion it would be boring, if every desktop tried to do the same thing. And there wouldn't be any innovation, if no one tried to do things differently.

Actually that's one of the main reasons I use Syncthing: It doesn't need a server, as it is a peer-to-peer architecture. Unlike a centralised solution (cloud storage, Nextcloud, etc.) devices sync directly with each other. If they are on the same local network, you get to enjoy the full bandwidth of your local network. If they need to sync over a long distance over the internet, you are limited by the upload and download speeds of your internet provider, just like with centralised storage.

I have a server that serves as an introducer, so I don't have to connect each device with every other device manually. But the server doesn't need to be available once all devices are connected with each other.

Syncing continues to work without it for as long as I don't reinstall any of the other devices. And even if I'd reinstall a device, I could delegate any other device to be the introducer or connect the devices manually with each other. It really is quite robust and fail-safe.

When I was still new to Linux I also had these phases from time to time where I went back to Windows, used mainstream software, like Microsoft Office, etc.. I was still undecided if Linux was really worth all the hassle and I wasn't quite settled on either side.

But I always returned to Linux for whatever reason. Probably because using Windows just didn't feel right ... The times where I returned to Windows got rarer and shorter the older I got. The last time I used Windows for an extensive amount of time was during the Windows 10 beta period. I even had a Windows Phone for a year! I returned to Linux roughly once Windows 10 was released as stable (funnily enough).

I believe that you are likely in a very similar situation at the moment as I was. I think you might just need some time to settle with something and get comfortable. ;)

Haha, that's what I was thinking as well when I first discovered it. Glad you found it through my post!

I took my handwritten notes with PDF Annotator in a Windows VM for over three years ...

Have you considered a fixed release in combination with rolling applications (i. e. Flatpak, Snap)?

If you choose Fedora (preferably one of the atomic variants, like Silverblue), you would also get a rolling kernel and rolling KDE Plasma desktop, so overall the experience can be quite close to a rolling release distribution if you install the desktop applications via Flatpak.

Ubuntu "interim" (non-LTS) releases are usually also fairly current and could be a good choice if you don't mind Snap. There's also the option of following the Ubuntu "devel" branch, which always refers to the current pre-release version of Ubuntu (e. g. 24.04 at the moment) and is rolling.

Just wanted to give you a different direction to think about. ;)

Have you enabled virtualisation support in your BIOS/UEFI? Many vendors ship their hardware with this switched off by default (and some hardware actually doesn't support it at all).

I don't have any issues with Xwayland and simultaneous key presses. Tested with Bottles (i. e. WINE), BeamNG (native Linux build) and the games from SCS Software (also Linux-native). I am running Fedora 38 Silverblue with an AMD RX 5500 XT GPU.

As far as I know, companies don't have to comply yet with the Digital Markets Act. That's most likely the reason why the WebKit restriction is still in place.

Joplin has export options itself, but I just don't like how Joplin manages notes on a filesystem. If it can be done nicely (see Obsidian), why bother with something needlessly complex (file structure, need to sync with the filesystem, etc.)?

But everyone has different requirements and for the right person, Joplin can certainly be a good solution. ;)

I didn't know about Logseq! Looks really interesting and since there's a Flatpak available, I'll give it a try. Thanks for mentioning it!