Well, I settled on a Ubuntu derivative so I guess it’s in the family. It could just as easily have been Fedora though.

My laptop gets shut down every night, booted every morning. If I suspend it sometimes spontaneously wakes later, but boot is so fast anyway so it’s fine.

My server gets updated and rebooted weekly. I don’t bother checking CVE bulletins, I just upgrade weekly.

I have Intel iGPU and Nvidia dGPU on my laptop, it works perfectly with Prime offload. I never need to switch, it uses Intel for desktop/VA-API and offload for games. No issues, at all on my distribution.

Anyway, every thread have your kind of unhelpful comment. The thing is some people have Nvidia, some have AMD and AMD also have bugs. Let’s try to make everyone happy, not everyone have piles of money to throw after new hardware.

Yes, it’s because it keeps track on object lifetimes and data access when sharing objects, even across threads. It means that once things compiles a whole category of common and often difficult to debug errors are gone. It means much less time debugging and fewer issues once in the hands of the end user. There can still be bugs but it’s more about logical errors than difficult memory issues.

As a C++ dev for 20 years, I love Rust. Humans are fallible, even if endeavouring to use safe patterns. Might as well just let the compiler use some CPU cycles on that.

The GNU Image Manipulation Program introduced optional single-window mode in version 2.8, which was released on May 3, 2012. It was made default starting with version 2.10, which was released on April 27, 2018.

Here’s what warrants a major version bump: GIMP 3.0.

I always end up with SF Pro Display for my desktop. For terminal I’m happy with several mentioned here.

Yes I encountered that when I used Tumbleweed on my laptop, the solution was to run “sudo prime-select boot offload”. It set up my laptop to use iGPU for desktop environment and NV offload for gaming. I made it part of my update script. No idea why that wasn’t handled better.

But generally I’m done with rolling distros, I now use an Ubuntu derivative that still keeps kernel and mesa quite up to date, I enjoy a stable environment.

It’s a temporary thing and it’s likly Kent will just spend the time too continue development and prepare patches for next cycle instead. The ambition is to take it out of Experimental status sometime in the next year so there’s at least motivation to figure out these things. During the delay testers of this FS can still submit bug reports.

It is default XWayland and will only fallback to Wayland if no XWayland found.

It has replaced idly making selection squares on the desktop.

I started with Slackware in the late nineties. Have been through Redhat, Suse, Ubuntu, Arch, Tumbleweed. These days I just can’t be bothered, I just want to game and code and I prefer an out of the box well configured Ubuntu derivative, they also upgrade easily and have lots of application compatibility - mostly everyone provides .deb packages. I could also choose Fedora for these reasons.

So now on Pop!_OS 24.04. Pop is has a stable/lts base but still gets Mesa/Nvidia/Kernel updates on a regular basis. I use it mainly for gaming and Rust dev, writing some COSMIC applets as well.

COSMIC Alpha does still have problems with some games but not the games I play.

Yeah, GuildWars2, Valheim, Pathfinder WotR, etc. those sort of games… So I’m a bit niche, some gamers have more issues than I.

I got a gnome-session installed for games that have problems with COSMIC but fortunately haven’t needed it for a while now.

I started with Slackware in the nineties, have been through Redhat, Suse, Ubuntu, Arch, Tumbleweed.

I could use anything really but these days my focus have moved; I kinda just want functional and well configured up front. Using Pop!_OS 24 alpha on my gaming/dev laptop, it works well/is well put together and I’m having fun writing COSMIC apps. I’m using Ubuntu on a few servers, I picked it many years ago and they’ve been through a number of painless upgrades.

GIMP 3.0 makes it a lot easier for devs to add functionality and they’re starting a UX working group.

But I find it usable, I’ve been using it weekly for a very long time. I’m happy to see development picking up though with more people joining.

It’s certainly safer though one can probably still do some damage in /etc, if determined.

There are some other differences, for example Pop!_OS while on a LTS base still gets regular updates of kernel, Mesa and Nvidia drivers which is nice.

I believe the EU redirected open source funding to LLM/“AI”. Germany’s Sovereign Tech Fund on the other hand had its budget increased.

You always have to consider the sources of such whispers, otherwise it means very little. The devs, who are few and works on evenings because they have day jobs, a well-know open source issue for many projects, were clear about when they started in earnest on getting 3.0 done, less than 3 years ago. Until then they’ve spent most of their time adding features to 2.10 and the 2.9 branch was more of a long lived testing ground with occational test releases that cause talk sometimes. The aim was RC primo or medio this year, they’re only slightly late.

But I get the feeling more devs are starting to contribute now it’s near 3.0, maybe because the new architecture actually makes it easier. So there’s hope a lot will start to happen. There’s even a UI working group.

I’m running the 2.9 nightly, it’s better in a multitude of little ways as well as having a number of new features.

And one less thing to waste time on for experienced users.

This is a good thing, it is much needed for Snap and Flatpak and will make sandboxed applications less confusing for those who don’t grog flatseal/kde-settings/etc. and adds convenience for everyone.