Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Any iMac 5k users test this yet? I'd rather skip this if it is still bricking it like the last two betas.
 
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.
 
...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.

Don't have the same coding resources as MS i think. Besides the culture at MS is different (patch Tuesday).
 
No, it's actually alot more snappier. A much accepted improvement.

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.

----------

...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.

I'm not sure if it's a matter of not caring, but they are definitely not getting the coverage that they need. I sure hope that they are aware of the glaring problems...
 
Preview.app is still broken (only displays a transparent window/blank window). Also, other apps still have UI issues (like PowerPoint, ReadKit). VMware Fusion is still dog slow as well. None of these issues existed with 10.10.1.
 
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?


Chrome works again! Since Chrome did not update while it was in crash city, I'm guessing the deprecated API were restored.
 
A user on 9to5Mac confirms 10.10.2 is still doing the blank screen after waking from sleep or rebooting. So those who saw these issues from previous 10.10.2 betas might want to skip this one as well unless Apple asks you to test it.

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

Care to tell us which page, so we can test it too?

Is it something like the Verge?
 
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.

I'm not disagreeing - there's a lot of little things in both OS X and iOS that have been bugging me. I don't recall being this frustrated with previous releases.
 
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.
 
Culture is the big thing,I think. Microsoft it's a software company, Apple is a hardware company that makes software.

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.
 
Last edited:
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?

Not so. Chrome wasn't calling a deprecated API point, Apple changed an internal API for Yosemite (added a parameter) and in the first cut of 10.0.2 they removed the old version thinking they had changed all places in their code which called it. However there was still at least one they hadn't fixed, it called the old method and crashed.

The Chrome team were able to make a pretty simple reproducible case which showed the issue and sent it to Apple a couple of days back.

Either they put the method back, or fixed up the place of their own code which was calling the old, removed one. I'll look after I install it, this beta sounds a bit better than the last.
 
I'm seeing new behaviour in Mail.

When deleting a message the message scrolls up, in the list view ... This didn't happen for me in previous versions. It's somewhat iOS like... rather than sideways... it's upwards.
 
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.

I couldn't have said it better myself. They might as well go back to the longer release cycle they had before since now it takes an average of six months before a new OS X is bug-free enough to be usable.
 
Hoping they solved the "Always visible Bluetooth issue" on previous 2012 Mac models
Any news?
 
Last edited:
Yosemite Font Issue

I was wondering if there is a fix for the font for non-retina displays? It's not clear and crisp at times. Has it been darkened or is there an option to darken the font in this beta? Any choices to increase font size system wide? I've already tried out all the various options in sys pref and nothing works.
 
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.

I completely agree. We are almost two months since the release date and I still cannot reliably connect to WIFI and I cannot use my magic mouse or keyboard because there are issues with bluetooth. There is definitely a quality control issue at Apple - they've proven this several times recently.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.