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.

I remember those times too. The difference today is that there are so many more libraries and projects use those libraries a lot more often.

So using configure and make means that the user also has the responsibility of ensuring all those libraries are up to date. Which again if we’re talking about not using binary install, each also need a regular configure/make process too. It’s not that unusual for large packages to have dependencies on 100+ libraries. At which point building and maintaining the build for all of them yourself becomes untenable really. However I think gentoo exists to automate a lot of this while still building from source.

I understand why binaries with references to other binary packages for prerequisites are used. I also understand where the limits of this are and why the AppImage/Flatpak/snaps exist. I just don’t particularly like the latter as a concept. But accept there’s times you might need them.

Last time I ran a corporate-made installer, it caused massive graphical glitches and lock-ups after waking from sleep. It basically gave my system computer-AIDS.

That’s why I never run scripts which are too long for me to easily understand outside a sandbox. Official distro repositories and Flatpaks are the only sources I have some level of trust in.

Blame the thousands of supply chain attacks.

Better cli experience and the permission prompts are two that come to mind.

obligatory “there is always a relevant xkcd”