Yes! In fact, Chromium was originally a fork of WebKit, as WebKit was a fork of KHTML. In both cases the codebases have diverged quite significantly though.

The core of Safari (WebKit) is open source. If it weren’t they’d be violating the GPL license of KHTML.

Good chicken

Lolno

No handouts for the poor. Only handouts for the rich.

Kubuntu, because it’s the most solid distro I’ve used that meets my needs.

It may surprise you to see how many Debian contributors are doing so on Canonical’s payroll.

Isn’t Pop OS just System76’s spin on Ubuntu?

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???

That link includes a whole lot of old things as well as blog posts about how they sped up the performance of the Firefox snap, after which there doesn’t seem to be much, if any, further evidence of the snap being slow.

The claim that snaps are a Canonical NIH thing is falsified by those two facts. Even if Canonical said “okay, we’ll distribute desktop apps with Flatpak,” that wouldn’t affect the vast majority of their ongoing effort for snaps, which are related to things that Flatpak simply doesn’t do. Instead, they’d have the separate work of making the moving target of flatpaks work with their snap-based systems such as Ubuntu Core while still having to fully maintain that snap based ecosystem for the enterprise customers who use it for things that Flatpak simply doesn’t do.

Good thing grep exists!

I don’t like snaps because it’s just another Canonical NIH thing. Everyone else agreed on flatpak which seems to have a good design with portals and all and being fully open.

Snaps both predate flatpak and do things that Flatpaks are not designed to do.

Canonical have also been a part of the desktop portals standard for a very long time, as they’ve been a part of how snaps do things.

Are they though? They were at one point, but even then I’ve not seen comparative slowness compared to the equivalent Flatpaks. In some cases I’ve seen them be slow compared to native packages, but even that seems to have all but disappeared for me.

That’s some weak coffee…

Flatpak has long had the ability to dump the contents of a snap into it, because snaps had already solved many of the build issues flatpaks were struggling with and they used similar runtimes for their sandboxing. It’s also a convenient way to convert apps over, since many apps got packaged as snaps before flatpak was really usable.

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.

And in a mirror universe where that decision got made someone’s arguing “maybe we shouldn’t have cut funding to Israel if it meant allowing the genocide in Ukraine.”