In Linux you have to do sudo systemctl disable snapd, which produces a warning about snapd.socket. New users sometimes get a little freaked out about disabling stuff in systemd, especially after they find out what systemd is and does and how important it is. They’re afraid of bricking their installation and you have to be like “no, that won’t happen. Yes, I’m sure it won’t happen. No, you don’t need to reboot. Just replace disable with stop in those commands again and it won’t run anymore. Yes, I’m sure it’ll be fine.” So the commands are trivial, but the psychological toll of doing stuff via the command line that you perceive as dangerous, for truly novice Linux users, isn’t to be underestimated.
In Linux you have to do sudo systemctl disable snapd, which produces a warning about snapd.socket. New users sometimes get a little freaked out about disabling stuff in systemd, especially after they find out what systemd is and does and how important it is. They’re afraid of bricking their installation and you have to be like “no, that won’t happen. Yes, I’m sure it won’t happen. No, you don’t need to reboot. Just replace disable with stop in those commands again and it won’t run anymore. Yes, I’m sure it’ll be fine.” So the commands are trivial, but the psychological toll of doing stuff via the command line that you perceive as dangerous, for truly novice Linux users, isn’t to be underestimated.
Did you respond to the right comment? I was trying to say that instructing new/novice users to disable snap updates is probably a bad idea.
I read that as “should be trivial,” not “shouldn’t.” In my defense, I don’t have my glasses on right now. 🤓