you are viewing a single comment's thread
view the rest of the comments
[–] 36 points 5 hours ago (4 children)

Good change.

  • It helps the less tech savvy users,
  • It actually forces developers to write their app properly.

Software should not operate at a privileged level “just in case”, but rather have a well-defined functional boundary.

  • source
  • hideshow 4 child comments
  • [–] 9 points 4 hours ago (3 children)

    It's not clear exactly what Apple is going to impose here. In principle, trying to ensure users understand the implications of a permission is good. In practice, Apple is famous for keeping users from making decisions they might reasonably want to make on phones, and it's starting to creep into the Mac; installing an app Apple hasn't signed requires the command line, for example.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 55 minutes ago

    installing an app Apple hasn’t signed requires the command line, for example

    Yeah this is the reason I've avoided Macs for so long. I get giving the user a warning but not providing any sort of prompt to override the warning, and hiding it in a terminal command is ridiculous .

    There was also one time I tried to simply turn off Bluetooth and it was just like "I'm sorry Dave, I can't do that". And I was like WTF, absolutely not .

  • source
  • parent
  • [–] 7 points 2 hours ago (1 child)

    Apple also has a history of requiring excessively scary permission requests for things that Apple apps do without prompting. They abuse the permission system to foster a sense that Apple products are safe and any competitor is dangerous.

  • source
  • parent
  • hideshow 1 child comment