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.
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.
That is the behaviour that’s built for when an upgrade through a “classic” package manager (e.g. apt, dnf) updates Firefox while it’s still running. The only way I can think of that you’d get that with a snap is if you’re intentionally bypassing the confinement (e.g. by running /snap/firefox/current/usr/lib/firefox/firefox
directly, which can also massively mess with other things since Firefox won’t be running in the core22
environment it expects).
If you’re using the snap as expected (e.g. opening the .desktop
file in /var/lib/snapd/desktop/applications/
, running /snap/bin/firefox
or running snap run firefox
), snapd won’t replace /snap/firefox/current
until you no longer have any processes from that snap running. Instead you’ll get a desktop notification to close and restart Firefox to update it, and two weeks to either do so or to run snap refresh --hold firefox
to prevent the update (or something like snap refresh --hold=6w firefox
to hold the refresh for 6 weeks). Depending on what graphical updater you have, you may also have the ability to hold the update through that updater.
Are you sure you’re running the Firefox snap? Because that sounds pretty much precisely like the expected behaviour if someone had gone to lengths to avoid using the snap.
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.”
The updates download in the background and will install when you exit the snapped app. If you really don’t want automatic updates, you can run snap refresh --hold
to hold all automatic updates or add a snap name to hold updates for that snap.
A built-in way to have services running (which is why openprinting can make a snap of CUPS but AFAICT can’t make a Flatpak).
Cars. They ruin cities.
OrderS of magnitude? How heavy does this guy think we are?
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
My laptop had 2 USB4 with type C connectors, a USB 3.2 type A connector and a USB 3.2 type C connector, but recently it’s had an HDMI connector instead of the 3.2 type C.
It’s a distilled version that becomes a potion in your stomach. There are several versions of this, my favourite of which is “instant bubbling potion, just add water”
Especially if you’re using raid5 for multi disk.
Kinda amazing how some people would rather spend their energy denying well-known facts than just admit that both players are kinda crappy…
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?
If meatballs and mashed potatoes with lingonberry sauce are against the Geneva convention it’s probably time we had on Oslo convention.
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.