I think I might know the cause for macOS/iOS's recent super bugginess.

grahamf

Member
Nov 19, 2012
324
0
16
Visit site
This is conjecture based on the following tidbits.

Apple has the tendency to launch a new OS with a bug, fix the bug, then have the exact same bug pop up again in a newer release

Apple is known to be a very secretive company, even internally

Insider reports indicates that Apple is a very high pressure work environment.

The former indicates that the development team and the support team are isolated with very little contact with each other, while the latter two are the perfect recipe for the worst coding practice ever: poorly documented spaghetti code.

No doubt that for the longest time Apple developers have spent years working on their own projects with little oversight or incentive to fully document and get a second set of eyes on their code, which has led to an accumulation of hidden and complicated bugs lost in code blocks that not even the original developer fully understands the function of, compounded with he fact that developers are isolated from any sort of feedback from the support teams or users that can notify them of severe bugs in their code. It seems like Apple only now has realized this, but they are left with a legacy of bad code that will take a long time to resolve.

Anyone think this is likely what has happened?
 

Members online

No members online now.

Forum statistics

Threads
323,183
Messages
2,243,404
Members
428,036
Latest member
Tallgeeselll05