• Warzone 2100
• OpenTTD
• 0 A.D.
• OpenRCT2

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?

I switched pharmacies and holy shit do the different Adderall generics taste different. I’m stuck now with the Meijer pharmacy because I can’t go back to the bitter vomit-inducing crap I was getting at Rite Aid.

I believe the two requirements for level 2 are 200 VAC and 2 kW. A 208V 30A oven outlet in a typical American apartment is level 2, but so is a 240V, 15 A plug in a typical European, well, any room.

The 240V, 30A+ portable EVSEs many cars come with are level 2, though they are often also able to do level 1 charging if they work on 120V outlets.

That’s a very “we’ll fix it in software!” solution

Many cars with CCS type 1 will lock a J1772 the same way they lock the type 1 port. Sad the Volt doesn’t.

In much of the world the wall plug is the bottom end of level 2.

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.

It depends what you’re trying to accomplish. For me, having the ability to essentially use Lego to put together my system is one of the great features of both snap and nix that Flatpak doesn’t cover.

There are plenty of use cases that snap provides that flatpak doesn’t - they only compete in a subset of snap’s functionality. For example, flatpak does not (and is not designed to) provide a way to use it to distribute kernels or system services.