Linux distros typically have 2-3 different ways to install applications and multiple mechanisms for updating/maintaining,
Windows ways to install applications:
hunt down an installer either exe or msi file, or a zip which you unextract somewhere which doesn’t then create desktop icons and then scattered all aroundu
Windows store, just like any other application store by MacOS or Linux only shit
Winget, cli installer just like under Linux but actually decent
chocolatey, aaaah just stop!
On windows, they have a registration scheme where installers log to a common OS level application management on what to run to uninstall.
Right but in practice nobody really uses the Windows store, and winget, chocolatey etc. are only used by geeks. For normal users it’s always
Download .exe or .msi
Double click it.
Follow the instructions.
On Linux you have:
apt, dnf, etc. - pretty reliable but only really work from the command line (I have yet to use a “friendly” store frontend that actually works well), and you almost always get an outdated version of the software.
Snap or Flatpak - the idea is there, but again I have yet to actually use one of these successfully. They always have issues with GUI styling (e.g. icons not working), or permissions, or integration or something.
Compiling from source - no Windows software requires this but it’s not uncommon on Linux.
Also it’s relatively common for Linux software not to bundle its dependencies. I work for a company that makes commercial Linux software and they bundle Python (yes it’s bad), but that depends on libffi and they don’t bundle that. So it only works on distros that happen to have the specific ABI version of libffi that it requires. And you have to install it yourself. This is obviously dumb but it’s the sort of thing you have to deal with on Linux that is simply never an issue on Windows or Mac.
Dependencies only become an issue if you don’t distribute your source (allowing distros or individuals to compile against the shared libraries they actually have installed, and patch out minor compatibility issues). Since closed-source is frowned upon in the Linux world, it’s unsurprising that there are various sorts of pressure to Not Do That.
Since closed-source is frowned upon in the Linux world
Indeed, this is a root cause of the problem. But it is a problem. The Linux community needs to get off its high horse and make distribution of binary programs (which may or may not be open source) work properly.
Snap and Flatpak are definitely a step in the right direction at least.
On windows, they have a registration scheme where installers log to a common OS level application management on what to run to uninstall.
Yup sounds absolute reasonable… Wtf?
What’s wrong with that? When I was cleaning out Windows recently, I was happy that I didn’t have to hunt down uninstall scripts in every program directory I wanted to remove.
Maybe I’m a bit jaded as I remember the time where windows application didn’t even came with a basic uninstaller and didn’t relied on InstallShield instead used their own installer.
Also I don’t think that there is actually such log, and that “OS level application management” is just the good old “Programs and Features” dialog where it simply registers the path to the uninstaller.
On Linux on the other hand the applications place their stuff in well defined directories and the install script has to deliver the file manifest (and where to copy its content) otherwise the application or library would simply not work. Flatpak kinda does the same but uses a dedicated directory in the users home directory, Snaps uuhm I don’t touch canonical stuff with a ten foot pole, AppImage just delete the file and your are golden.
Windows ways to install applications:
Yup sounds absolute reasonable… Wtf?
Right but in practice nobody really uses the Windows store, and winget, chocolatey etc. are only used by geeks. For normal users it’s always
On Linux you have:
Also it’s relatively common for Linux software not to bundle its dependencies. I work for a company that makes commercial Linux software and they bundle Python (yes it’s bad), but that depends on libffi and they don’t bundle that. So it only works on distros that happen to have the specific ABI version of libffi that it requires. And you have to install it yourself. This is obviously dumb but it’s the sort of thing you have to deal with on Linux that is simply never an issue on Windows or Mac.
Dependencies only become an issue if you don’t distribute your source (allowing distros or individuals to compile against the shared libraries they actually have installed, and patch out minor compatibility issues). Since closed-source is frowned upon in the Linux world, it’s unsurprising that there are various sorts of pressure to Not Do That.
Indeed, this is a root cause of the problem. But it is a problem. The Linux community needs to get off its high horse and make distribution of binary programs (which may or may not be open source) work properly.
Snap and Flatpak are definitely a step in the right direction at least.
ok.
What’s wrong with that? When I was cleaning out Windows recently, I was happy that I didn’t have to hunt down uninstall scripts in every program directory I wanted to remove.
Maybe I’m a bit jaded as I remember the time where windows application didn’t even came with a basic uninstaller and didn’t relied on InstallShield instead used their own installer.
Also I don’t think that there is actually such log, and that “OS level application management” is just the good old “Programs and Features” dialog where it simply registers the path to the uninstaller.
On Linux on the other hand the applications place their stuff in well defined directories and the install script has to deliver the file manifest (and where to copy its content) otherwise the application or library would simply not work. Flatpak kinda does the same but uses a dedicated directory in the users home directory, Snaps uuhm I don’t touch canonical stuff with a ten foot pole, AppImage just delete the file and your are golden.
That’s what I took that to mean, too. And it’s sufficient. It allows the OS to provide a single point from which to uninstall all programs.
Well then, when that’s sufficient. Have you checked
%AppData%(Local, Roaming, LocalLow) for any residue?What I meant is that the “registering with the OS” part is sufficient. If the uninstallers suck, no operating system can do anything about that.