Just exploring 🌎
Studying German 🇩🇪
Interests: Technology, Philosophy, Physics & Music.
| GitLab | https://gitlab.com/mac_alice |
| Matrix | @alice_mac:matrix.org |
@potatomeow it's less about what's preferred and more about safety, what is a minor inconvenience to someone like myself or you (1.5s spent inputting a password or Touch ID) is a massive life saver for standard users, the trade off of a few software engineers or sysadmins grumbling online isn't worth the amount of average users who prefer macOS systems for their consistency and safety.
This could prevent accidental user errors and decreases risk of malicious scripts closing applications.
@potatomeow to add, if it were just a prompt and not a password many users would accidentally hit yes without reading it and then complain when something breaks, the password forces them to stop and ensure it's the correct action.
Another note I believe you can enable authorisation via Touch ID then you don't need to input a password.
@potatomeow then run it with `sudo` in the terminal, the default behaviour should add safeguards to stop users with less knowledge on computing losing their work etc. these systems are designed for the general public as well.
The "negotiation" step is to ensure the user who may have less knowledge than you is aware of what is going to happen and the possible repercussions.
Yes the Linux option is preferred if you have the knowledge of what the command will do before execution.
I am an Apple Silicon binary fundamentalist. No Intel binaries allowed on my Mac, and Rosetta2 is The Devil. I didn’t spend all this money (so. much. money.) on an AS-powered MacBook Pro to run filthy Intel software on it!
So far, this has meant I miss out on:
Adobe Acrobat Reader.
Oh well 🤷🏻♂️
Party Seven