5 ms·
So the answer is to simply not trust Apple to release stable code? Surely the very existence of this answer, proves the point of the original question. Anything
by razormouse 7y ago
So the answer is to simply not trust Apple to release stable code? Surely the very existence of this answer, proves the point of the original question.
Anything else is just victim blaming.
- s_dev 7y ago>victim blaming Ah here, leave it out. All new software has new problems -- don't want the problems. Opt for tried and tested. Plenty of folk still happily purring along on older versions of macOS. There was a great article here the other day about a guy revising his approach to upgrading macOS every October instead choosing to evaluate the new features vs introducing change that can break things. Can't find it though atm.
- iClaudiusX 7y agoIt used to be that a release was tried and tested. Now everyone's an unpaid QA tester months after the official beta period is over. And the folk wisdom of "wait until x.1" keeps getting pushed further and further back to the point of futility.