Petr Škuta Apple he whipped himself a whip. It is often pilloried by users for bringing new features, but often with bugs. On the contrary, when a company decides to devote all its time to "ironing out" the system and optimizing it, it is again criticized for the lack of innovations.
After all, it was the same in the case of iOS 12. One group of users praised it because the system was really stable, fast, and most importantly, without major bugs. But another group of users complained that the XNUMXth version basically did not bring any new features and did not advance the system further.
S iOS 13 we are currently experiencing the opposite situation. There is a sufficient amount of new products, but they do not always work as they should. Apple already issued full series of patch updates and still not finished with tuning. Then around the corner is iOS 13.2 with mode Deep Fusion, which is already in its fourth beta version.
It could be interest you
Dan Pražák I'm missing the operating system didn't even escape macOS Catalina, although he did not bring too many essential innovations. However, users still report a number of problems that complicate their daily work, be it errors directly in the system or problems with drivers or software. And that's not to mention the fact that the general parts of the installation users froze at the settings screen.
All this gives the impression that Apple is not able to release a problem-free version of the software.
David Shayer v. attempts to explain the situation contribution to TidBITS. Shayer worked in Applu has over 18 years of experience as a developer on many projects. So he knows firsthand how software development in a company works and where mistakes are made.
Old system errors are not resolved
Apple has its own system for evaluating reported errors. Everything undergoes prioritization, where newer bugs are prioritized over older ones.
When a developer accidentally breaks some functionality, we call it a regression. He is expected to fix everything.
Once you report a bug, it will be evaluated by a QA engineer. If it finds that the bug has already appeared in previous builds of the software, it marks it as "non-regressive". It follows from the definition that it is not a new but an old error. The chance that someone will fix it is small.
I'm not saying that all teams work like that. But most of them do, and it drove me crazy. One team even made T-shirts that said "non-regressive." If a bug isn't regressive, they don't have to fix it. That's why, for example, the bug with uploading photos to iCloudor the error with contact synchronization may never be fixed.
One of the common mistakes in macOS Catalina when external graphics card freezes:
Shyer also rejects the claim that the software was once better. Apple it has many more customers today than it used to, so the software is under more scrutiny. In addition, everything is much more sophisticated. In other words, gone are the days when an OS X update was released for a small group of users. Today, the system reaches millions of devices at once after the release of an update.
Modern operating systems Applu have millions of lines of code. Your Mac, iPhone, iPad, Watch, AirPods a HomePod they constantly communicate with each other and iCloudApplications work in threads and communicate over the (imperfect) internet.
Subsequently, Shayer adds that testing such complex systems is a huge challenge that requires many resources. And even then, it doesn't always have to turn out well, which we already saw this year.
It could be interest you
I'm glad I wasn't tempted by the "dark mode" and have stayed on a fairly stable one for now. iOS 12.4 iPXS. I haven't encountered any errors yet.