Millions of lines of code. Millions to billions of user scenarios. Various routers and configurations.
...still a lot less variants than Windows and there are still so many glaring obvious bugs I feel that Apple just doesn't care about quality as much as they used to.
No, it's actually alot more snappier. A much accepted improvement.
...still a lot less variants than Windows and there are still so many glaring obvious bugs I feel that Apple just doesn't care about quality as much as they used to.
The Chrome crash has nothing to do with problems within Yosemite, it has to do with the Chrome team failing to check it on Yosemite. APIs were deprecated. If this latest release fixes the problem for you, then either you were updated to a newer version of Chrome or the deprecated APIs were restored. Do you know?
Yes, I just loaded a page with a very large form on it. This page used to take 3 minutes to display and now it displays instantly. Big speed boost
Hoping for TWO things fixed:
2) Safari "lag" when typing and general navigating
![]()
With so few variants of Apple computers out there I find it annoying they can't work out the majority of bugs before unleashing OSX on the public.
Don't have the same coding resources as MS i think. Besides the culture at MS is different (patch Tuesday).
Culture is the big thing,I think. Microsoft it's a software company, Apple is a hardware company that makes software.
The Chrome crash has nothing to do with problems within Yosemite, it has to do with the Chrome team failing to check it on Yosemite. APIs were deprecated. If this latest release fixes the problem for you, then either you were updated to a newer version of Chrome or the deprecated APIs were restored. Do you know?
Doubt that, Apple has always been a hardware company from the start. It does not explain the decline of QA coverage in the past few years. Their QA kinda went down starting from the move to annual release cycle for both OSes.
IMO, the reason is they're stretched out too thin and haven't been able to expand their resources to cover all products they're doing. Remember one time, they had to delay the OS X version in order to focus on a iOS release. Now, they probably took resources from the iOS team to work on Apple Watch, which probably took resources from the OS X and hardware teams as well.
IIRC, Microsoft actually designed their team structure to collaborate between several departments when working on projects that overlaps.
Apple is a collective of small isolated "startups", they do not collaborate between each other. That's a big problem when working massive projects like iOS and OS X. For an example, look at the AirDrop. That could've done better if both OS X and IOS teams work together on that.
It's the THIRD developer beta for 10.10.2, not second!
First had build 14C68k
Second had build 14C68m
Third has build 14C78c
No. They were not the same.
A general release should not necessarily be considered early adopter territory. That's what the beta program is for. There's no excuse for the problems to exist this far after Yosemite is released. There's a very obvious quality control problem within Apple, and I'm sure they are aware of it, too.