Apple Seeds OS X Mavericks 10.9.3 Build 13D55 to Developers

Apple also added support in previous builds of 10.9.3 for Slow-motion playback in QuickTime and QuickLook for videos with high frame rate. For example captured by iPhone 5s. This feature hasn't been mentioned in the thread.

655MB. Just kidding - I have no clue how big it is - but I miss those meaningless size of the download posts.

Downloading now. Just kidding - I'm not downloading it right now - but I miss those meaningless downloading now posts.

I've already explained why public beta testers can't see it yet.

You should read previous posts in this thread.

Do I have to start quoting myself?

I assume that, given the tone of this post, you must work for Apple? You must have some reason to expect everybody to just accept your word as the end-all-be-all.

I've already explained why public beta testers can't see it yet.



You should read previous posts in this thread.



Do I have to start quoting myself?

No, but you could get off your soap box...

There is a good reason for the delay in releasing it to public beta testers (or for that matter not releasing it at all to them).

Lets say the build is a disaster and ruins your mac. Developers are probably better at fixing it than the general public. So it makes sense to give it to them first - just in case it is a disaster.

Nonsense

Apple has way too many $billions in their pocket to being crowd-sourcing (and without any sort of monetary reward, to boot) beta-testing of an operating system. Hire more people, Apple. Apple could literally afford to have two thousand guys in a huge auditorium doing nothing but beta-testing OS X all day. They wouldn't reguire a huge salary, either. I'm sure a number of computer geeks out there would be willing to do that for $10/hour. It would come with the prestige of being an Apple employee ;)

Companies don't (or at least shouldn't) do public betas to cut costs, they do them to improve the quality of their software. Public betas might not even be cheaper than hiring people directly to do the testing: the company has to go through more support requests, more bug reports, more bandwidth used to distribute the betas, etc.

What makes public betas so useful, is that it brings more environments, users, use cases, and combinations of hardware and software to the testing, than you could ever arrange in a controlled testing environment. For example, the with more beta testers the issues with WD SmartWare (https://www.macrumors.com/2013/11/26/western-digital-releases-new-hard-drive-software-after-mavericks-data-loss/) might have been spotted well before Mavericks was released. It's much easier to recognize patterns, if you have more bug reports to work with.

Not showing up on Software Update yet :(

OMG. It not showing up for me either. Maybe there is something wrong. Did I violate the Terms and Conditions? Did Tim hear about the remark I made the other day? Wait, how would he know who I am. OMG... I am so freaking out because I don't see the update....

/s
:rolleyes:

Nonsense

It is nonsense, but you should provide more detail to justify your smug condemnation. Without evidence your words are just meaningless opinion, or should I say, nonsense.

There is a good reason for the delay in releasing it to public beta testers (or for that matter not releasing it at all to them).

Lets say the build is a disaster and ruins your mac. Developers are probably better at fixing it than the general public. So it makes sense to give it to them first - just in case it is a disaster.

Companies don't (or at least shouldn't) do public betas to cut costs, they do them to improve the quality of their software. Public betas might not even be cheaper than hiring people directly to do the testing: the company has to go through more support requests, more bug reports, more bandwidth used to distribute the betas, etc.

What makes public betas so useful, is that it brings more environments, users, use cases, and combinations of hardware and software to the testing, than you could ever arrange in a controlled testing environment. For example, the with more beta testers the issues with WD SmartWare (https://www.macrumors.com/2013/11/26/western-digital-releases-new-hard-drive-software-after-mavericks-data-loss/) might have been spotted well before Mavericks was released. It's much easier to recognize patterns, if you have more bug reports to work with.

Correct. In other words, consider the fact that in cases like this, you want a dirty environment to improve the stability of the OS. If you hire 10,000 guys to test things, they're going to start out with a clean OS install, do things in organized fashion and stuff like that. 99% of them are not likely to find anything wrong whereas having 1000 customers with very dirty and different OS environments with various tools, misconfiguration issues, and so on, they'll find bugs very quickly.

Just as humans will suffer badly from growing up in a pure clean environment and then being let out in the world as opposed to be being practically immune if they grew up dirty and being let out in the world.