To disallow control of the updates by the users is probably well-intended as some kind of a trade-off, but what if I don't want a new feature that is coming in

To disallow control of the updates by the users is probably well-intended as some kind of a trade-off, but what if I don't want a new feature that is coming in the next version? What if I already know it's broken in my system configuration -- I hope for a fix for 60 days, and then what? What if the fix never comes? Does my system stop working? What if I'm a business relying on that specific version? Do I just say "oh well" and close shop? And what about airgapped systems? I understand there's the "security", but then, on the other hand: 1. If snapd gets forked because of this, the snap ecosystem becomes fragmented and Canonical loses control of part of their baby. 2. If snapd stays as-is, and Canonical keeps preventing user control of the update cadence, then people will just run away from using snaps once the magical auto-updates create any high-profile problem. Lxd is a snap as well, so containers will be in the crosshairs. All in all it feels like a silly decision if you ask me.