taanegl

Damn, these rpm-ostree distroes are taking off. I mean tbf, having a “cloud native” approach (a two buzzword combo) with system images is kind of great for testing, and it shows people can now actually carve out some systems in a relatively effective manner. Good show!

That is supposing it is rpm-ostree, because ostree can actually rebase to an entire different distribution. There’s people getting arch working as an ostree install, and eventually, we’ll have gone over to a new dawn, where you don’t need to reinstall, just rebase.

Goddamn open source is awesome.

Friggin’ GIMP 2 is sun setting. GIMP 3 with everything replaced in GEGL and non-distructive editing is the new standard. Who tf needs Photoshop?

Thanks Microsoft for spotting that, and thanks to Google and CloudFlare for blocking or redirecting Polifyll.io network traffic.

Credit where credit is due.

Namaste.

Hopefully rpm-ostree is just the beginning. When SuSE Mint, Zorin, etc have some form of ostree tooling, then it’s over for you bitches, and by it being over for you bitches, i mean the need to do a full system reinstall will be over because you bitches can just rebase.

It truly will be the evolution of distro hopping, codifying a “of fuck, GO BACK” function by way of image handling, rather than barfing your operating system file system hierarchy on to your root partition like some caveman.

The future… is OCI images and layering, like in containers, because cloud native containers is the way - for the desktop… no, seriously. Stop laughing.

The RISC-V is an extensible ISA, so yes. All those vendor extensions are optional, when fabricating the processor, which can be replaced by other extensions over time.

Both Intel and AMD have had vendor extensions in the designs that they no longer use, even ones that have been “retracted” (i.e whatever in the heck Intel is doing with their AVX extensions).

But yeah, currently, there are a lot of proprietary extensions, which could still be declared as open hardware as well. So yeah.

Find the make and model of your system and search for it with “Linux”. This is a really easy way to avoid big problems, and finding a suitable distro for said system. It sucks installing a system, only to find out a certain boot flag needs to be turned off, or some kernel has a patch your system doesn’t like. Avoiding all that or even going into the situation prepared is much less stressful.

It also helps to know that with the freedom of Linux, there is a lot of difference in how systems are built, and that is a benefit and not a drawback.

I’d say that there are some differences, but whereas Plasma 3 to Plasma 4 design-wise broke the mold, going from 4 to 5 was seemingly less of a major version milestone and more of a major version touch up.

I’ve used both, a long time ago, and I might be off base here when comparing Plasma.4 with 5, but what’s also good about the transition from 5 to 6 is something called skeumorphism, i.e continuously developing a design language rather than making ground breaking changes. Plasma 6.1 hits a little higher mark, but considering all the UI work KDE has gone through the last year, it’s time to reap the rewards and hard work of the community.

That being said, backend wise, a ton of new stuff has come and even gone. The last years there’s even been an attempt to rewrite a lot of old stuff into modern code, in preparation for Wayland support in somecases- which was a doozy. Wayland is not an easy protocol to implement - or so I’ve heard.

We lost the cubic desktop, and got it back again, it’s been a wild ride. Kudos to the Plasma team for finally starting to catch up to GNOME in the UX department and that their efforts have been fruitful. I’ll be trying out Plasma 6.1 as my daily driver once it is released as stable.

I love GNOME, but Gnome Software is hot garbage. If KDE gets their gtk/adwaita tweaks in place, I might recommend Discover instead.

Also, arguably, by the most argumentative people, AppStream is also hot garbage, which is what was supposed to solve your problem regarding “too many package managers”.

I personally would wish AppStream didn’t suck and that it was also aware of NPM and crate packages. They’ve sort of been forgotten or relegated “developer tools”… even though you can pull full applications and system libraries.

How many “it’s 2025 already” problems do we have to encounter this year?