|
Honestly, the fact that to install software you have to go on a site, download an installer, and run it, is one of the reasons why I don't like Windows. Not only that thing is time consuming and cannot be easily automated, but it's error prone, you are likely to find in the first Google results not the official website of the software but some other site like Softonic that with the software also installs bloatware/malware/toolbars/etc. Of course an expert user can distinguish the official site from a scam, but usually the average computer user can't. What I like about Linux is just that you type in a terminal (or you use one of the many GUI that exist) `sudo apt install <software name>` and a version of that software, along with its dependencies, it is installed. And not only installed, but packaged, if needed patched, and tested to work along with other software in the distribution. When I install Windows I spend at least 1 hours going to every website of software that I need, download the installer, run the installer, click next, next, next, and repeat. With Linux I can just type in a single command every software that I need, let it run and install it, while I do other things. And when you need to uninstall a software? On Windows you need the uninstaller, that if it was not created correctly, or created at all, will leave a lot of stuff on the system, files, registry keys, broken links, cache files, etc that you need to remove either manually or with some "cleaner" programs that do more harm than good, for that reason an installation of Windows needs to be formatted every X years cause of the accumulated crap. From a developer point of view, and I've done many times, writing an installer for Windows, even using open source frameworks like NSIS, is a manual operation that is time consuming, can induce in errors, you need to learn a specific scripting language, etc, while making a package for Ubuntu/Debian (for example) is a simple operation, as simple as put the files of your software in a directory, put in a metadata file, and launch a command to produce the package. Most build systems (automake, cmake) already can create deb packages automatically with commonly used plugins. |