> Or, macOS: Is it a .dmg with an .app that you drag to Applications?

   - In 98% of cases it is a .dmg with .app ... so drag and drop or App Store install.
   - 1% of cases it is a standard installer and that is mostly because the developer is old-school and too lazy to make a .app (e.g. here's looking at you Microsoft)
   - The remaining 1% (Homebrew/Macports) is really for the power-user, and in most cases you can just download a pre-compiled mac binary from the developers Github anyway.

For example I have never used Homebrew/Macports because my 1% power-user software has been available through the developer's Github (e.g. `bazel` etc. all publish mac release binaries )

> Meanwhile, 99% of my Linux software is "apt install foo" and that's it.

But `apt install foo` is a synonym for "custom installer that does who knows what" and/or "tar.gz with random crap in it"

Why ?

Your average user will blindly follow `trust me, sudo curl foo | bash` ...

And your average user is unlikely to look at the apt package build rules and/or source and/or dependency list and in the majority of cases will just answer `Y` to any questions from `apt`.