There are keys to configure when, and if, you get updates, https://snapcraft.io/docs/keeping-snaps-up-to-date
The total Linux desktop installation base is around 2.7%. Without automation, the Linux desktop does not look like it will attract any significant number of Windows users.
One gets a maximum of 60 days, that is all. Through a snap proxy it's possible to hold off longer, but then the proxy needs to talk with the snap store periodically.
Why people are upset is, I believe, that Canonical forces people to accept any and all changes to the installed software, without being able to guarantee perfect backwards compatibility for all upgrades. Obviously, neither Canonical nor anyone else can make that kind of promise for all software out there.
Canonical should not force updates on people; let people take care of backwards compatibility; let users turn the auto-update on and off and allow users also to freeze package versions (and their system configuration), if the users so please.
Also, not sure I understand the point about automation. There is automation already today in Ubuntu through autoupdating .deb packages. It is nothing inherently new in Snaps.
One problem with measuring Linux desktop installation base is that Linux users are often the people who turn off telemetry, call-home, employ DNT, run ad blockers, run third party script blockers, and so on. I wonder how much this skews the results.
You can "snap download" and "snap install" to bypass any updates.
Do you mean the obvious `sudo snap set system refresh.hold="$(date --date=+100years +%Y-%m-%dT%H:%M:%S%:z)"`? (no error)
edit: Ah, that silently stops working after 60 days, nvm.
So we're the beta testers for Snap. Awesome. Nothing I want to do more on my day-to-day desktop than to be an outsource QA team to debug Ubuntu's software. Thanks for making 'beta test' the default, just like with pulseaudio and systemd. I look forward to the one day in the future when snap doesn't suck too. Except, nope. No more Ubuntu.
I guess tossing Windows in there is some ad homen attempt to deflect, because the comment doesn't otherwise make any sense. Is "we'll screw our users until our software works reliably" somehow an answer to the M$ hegemony?
It will upgrade a running application without telling the user. Then it will remount all folders in use by the running application in read only mode. As such, your chromium will start misbehaving, crashing, extensions will start failing, it won't save cookies or remember tabs after restart. DBeaver won't be saving your .sql scripts. Snap developers think users are precogs. That users without any foreshadowing will close application before snap silently upgrades it behind the scenes.
Also Snap does really weird things as a container. I run multiple VPNs each within own network namespace. So something as simple as :
as root: ip netns exec myVPN chromium fails with execv failed: Permission denied
Both of these problems exists for years.