undefined | Better HN

0 pointsyoz-y8y ago0 comments

Maybe. But this particular bug happened precisely because Apple has changed _something_ in macOS. Also this something was probably quite profound since it has impacted a part of software that, at least from the outside, haven't changed much since a long time.

A lot of macOS users would actually prefer Apple to do less with it than what they are currently doing.

0 comments

hellofunk8y ago

> this particular bug happened precisely because Apple has changed _something_ in macOS

I don't know much about this bug but I have seen several reports that the bug has actually existed quite some time and is not new, only the publicity surrounding it is now shining a bright light on it.

yoz-yOP8y ago

I thought it was confirmed that it is new to High Sierra, it was indeed lingering on forums as a "administrator hint" though.

hellofunk8y ago

I think you are right, but it's still been in the wild for several months, despite that Apple just realized a comment claiming they discovered the problem yesterday.

j / k navigate · click thread line to collapse

0 pointsyoz-y8y ago0 comments

A lot of macOS users would actually prefer Apple to do less with it than what they are currently doing.

0 comments

hellofunk8y ago

> this particular bug happened precisely because Apple has changed _something_ in macOS

yoz-yOP8y ago

I thought it was confirmed that it is new to High Sierra, it was indeed lingering on forums as a "administrator hint" though.

hellofunk8y ago

I think you are right, but it's still been in the wild for several months, despite that Apple just realized a comment claiming they discovered the problem yesterday.

j / k navigate · click thread line to collapse