focher
About
- Username
- focher
- Joined
- Visits
- 107
- Last Active
- Roles
- member
- Points
- 425
- Badges
- 1
- Posts
- 688
Reactions
-
iMac Pro debuts custom Apple T2 chip to handle secure boot, password encryption, more
-
iMac Pro debuts custom Apple T2 chip to handle secure boot, password encryption, more
anome said:Interesting that there's no FaceID.
-
CrossOver 17 ships, lets Mac users run Windows versions of Microsoft Office 2016, Quicken ...
pigybank said:If you’re going to virtualization VMWare is the way to go. Office 365 essentially has parity between Mac and Widows versions.
2. Office 365 absolutely does not have feature parity between the versions. Even MS doesn’t make that claim. -
Apple's iMac Pro model number pegged as 'A1862' ahead of expected Dec. launch
-
Apple software sees disastrous, embarrassing week with iOS springboard crash, macOS root u...
A lot of ridiculous views in this forum.
First, no one will be fired for these bugs. Primarily because it's a piss poor way to manage an organization to set the standard of zero tolerance for mistakes. Second, there's no single person or set of people that can be blamed. This was an overall process failure, and the best people to address it are the ones who already are running the process ... so long as they recognize the problem and have the attitude that constant improvement is the cornerstone of any build process.
Second, Apple has almost surely started to analyze and revise its QA processes to mitigate the risk of a repeat of these bugs.
Third, there was no previous period where Apple products did not have problems. There's no "magical version" of any software or hardware that didn't / doesn't / won't have issues to be fixed. Sticking with a specific device or software version may give an individual some satisfaction, and that's fine, but it's nothing more than a lone approach that doesn't apply to the scale Apple operates at.
I also think anyone who treats the root bug as a non-issue is just burying their head in the sand. We have absolutely no idea what the wide scale impact of that bug is in regards to systems that have been infected. It may be zero and it may be millions. We just don't know.