They don’t really compete. Dark table does image processing, whereas Digikam’s major strength is its library organization.

In Python it’s really hard!

def __eq__(self, other):
    ...

How do you even write those subscripted hyphens???

Containers are great, but I find Docker’s way of making container images to be pretty bad, personally. Fortunately you can use other tools to create OCI images and then copy them into Docker, as the runtime is pretty nice for dev machines.

I met Soumyadeep at this year’s Ubuntu Summit. Really nice guy, very excited about what he’s doing.

Is the F-Droid version abandoned? It crashes on startup on my phone.

Yeah, adding a separate microarchitecture like amd64v3 would be a separate item. They might be able to do that with amd64v3 overlay repos that only contain packages that most benefit from the newer microarchitecture.

Personal stuff goes in ~/Projects

Work stuff goes in ~/Work/Code

Especially if you’re using raid5 for multi disk.

Still pretty important given how many systems are using the 1.0 series.

Snaps have had a permission system for at least 5 years now.

I don’t have a good comparison for this since my Intel CPUs are from 2014 or earlier, but I was thoroughly impressed with how well my new AMD laptop did video encoding (compared to the only-as-expected bumps in performance otherwise). Do you have examples of how much better QuickSync is than VCN?

I’m quite aware. I’m currently a maintainer of packages in all three formats.

I simply don’t understand how this is any different from the fact that Ubuntu doesn’t include RPMs?

It’s the exclusivity to snaps and nothing else that bothers me. Like, you don’t have a choice but to use snap for some packages.

Seems like a weird take. Before snap came along this was true to the same extent of Ubuntu with Debs. The fact that they’re migrating some of the packages they maintain (that also happen to be the trickier ones to maintain as deb files) to snaps doesn’t prevent you from getting another repo that has the package as a deb and using that any more than your distro not having the latest version of an app prevents you from downloading and building a tarball.

¯\_(ツ)_/¯

The Ubuntu Core Desktop demo at SCALE this year actually got me pretty excited for my desktop in a snap, or at least for playing with that. The closest analogy I have is to NixOS, since it’s way more flexible than just an immutable base.

If I can get some sort of KDE Neon type distro with immutable apps and desktop, I could potentially switch my family over to that and manage it all remotely (really big deal since my family is spread across 3 continents). Landscape is pretty good at remotely managing Ubuntu Core (I’ve not found anything even close for NixOS), so I’m hopeful this would reduce my management work when my family’s current Chromebooks need replacing.

KDE is pretty tech neutral. They publish on Flathub too.

Personally I’m pretty excited about the snaps of more KDE apps, as it’ll allow me to have the latest KDE apps even on my systems where Flatpak just shits the bed.

Wayland was entirely unusable and mired in politics. (Still is mired in politics tbh.) So Canonical took the things they wanted, added things they needed to get it working, and called it Mir.

When Wayland finally became functional, they also made mir a Wayland compositor.

Some of the Wayland Frog protocols stuff is stuff that originated with Canonical trying to make Wayland usable before they took their ball and went home because the giants of the industry didn’t want to talk to a company of under 1000 people.

Much more appealing to me is running Android apps on Linux officially. I don’t want to use Android as my main system, but I sure as heck would love to have one or two Android apps available on my Linux Machines.

It’s not a perfect comparison, but if we go by the Steam Hardware Survey, the first item I can find on the list that’s not supported with the latest beta drivers is the GT 730, at 0.21% of users. And it’s from June 2014.

Its passmark score is 835, which is lower than the 9 year old Intel HD 520 (867). I somehow doubt though that driver support for Vulkan/Wayland will be the major blocker.