Yeah! Just use a browser. Make sure to click the right download button (not the 50 ads disguised as download buttons) to download an executable (just the installer). Then, run the installer and click “next” a bunch of times. Why would anyone want anything different?
And then, experience the joy of that program spreading its files to 6 different directories, all at different levels of your drive. Who cares about having a sensical file system that clearly separates system from user?
Choosing an install location is totally a Windows only thing. Every other OS has a notion of where binaries and libraries of applications are supposed to reside, except for Windows. This is why you can’t invoke anything manually installed from cmd just by typing the name of the application and hitting tab for filename completion. You HAVE TO cd to where the file physically resides, THEN type the name of the binary. Couldn’t be stupider if you ask me.
That works for single drive systems or 2 drive systems, but starts to become a problem when you have 5+ drives with no raid, so important applications can be installed to the faster, higher priority drive, while less critical ones can be installed to a slower one.
It’s one of those big things that is hard to adjust to coming from Windows.
Windows just doesn’t use the terminal and would rather you launch it from the start menu.
Yeah! Just use a browser. Make sure to click the right download button (not the 50 ads disguised as download buttons) to download an executable (just the installer). Then, run the installer and click “next” a bunch of times. Why would anyone want anything different?
And then, experience the joy of that program spreading its files to 6 different directories, all at different levels of your drive. Who cares about having a sensical file system that clearly separates system from user?
I’d still prefer it to the terminal. I get to choose installation locations and it’s easier to configure.
Choosing an install location is totally a Windows only thing. Every other OS has a notion of where binaries and libraries of applications are supposed to reside, except for Windows. This is why you can’t invoke anything manually installed from cmd just by typing the name of the application and hitting tab for filename completion. You HAVE TO cd to where the file physically resides, THEN type the name of the binary. Couldn’t be stupider if you ask me.
That works for single drive systems or 2 drive systems, but starts to become a problem when you have 5+ drives with no raid, so important applications can be installed to the faster, higher priority drive, while less critical ones can be installed to a slower one.
It’s one of those big things that is hard to adjust to coming from Windows.
Windows just doesn’t use the terminal and would rather you launch it from the start menu.