Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yes, but he took over iOS on October 29, 2012.
It is quite possible that the most problematic irritations in OSX ultimately rely on control over both OSs to get them fixed, given that they share so much code and that some features are introduced first in one, then in the other.

I could imagine, for example, in the past, that if an OSX person wanted to fix say, some aspect of sandboxing that was causing problems for OSX, he was told not to touch that code because it might cause problems for iOS. Now, with a unified head of both OSs, it's easier to get issues like that resolved IF the guy at the top wants them resolved.

Fair point.
 
Easy guys we will releasing in the coming weeks.We have a lot of work to do and we have some pleasant surprise for you on 10.8.3 Build.
 

Attachments

  • Screen Shot 2013-03-12 at 11.56.08 AM.png
    Screen Shot 2013-03-12 at 11.56.08 AM.png
    36.1 KB · Views: 1,709
Precisely. If Apple released this sooner, people would inevitably find some bug and complain that Apple should have taken their time.

Oh, and regarding your signature- GO BEARKATS! Just kidding... you beat us two years in a row, you have every right to be proud. :D

The bugs will still be there.
 
Does this fix the rmbp? Would be great! I paid a lot of cash for it and it still lags like hell.

I really hope so too. To be honest, my current experience with it is beta-like at best. Slow UI, very glitchy Safari, abysmal 2D+3D graphics performance,... Under bootcamp I have about 4x (!) the framerate in some apps. After finally deciding to get myself a new laptop after 6 years with the previous one, it would be nice to finally have it in working order...
 
The bugs will still be there.

Exactly my point. When people find the first bugs in 10.8.3, they'll ask why Apple didn't just release it sooner. If Apple released it sooner, they would have asked why Apple didn't just wait until it was ready.

We'll never know what critical bugs we avoided by Apple waiting for 10+ seeds to release this update. No piece of software, especially something as complex as an operating system, will ever be bug-free. Still though, I appreciate the effort that Apple is putting in to what would normally be a pretty minor update.
 
Quite the discussion about release sooner with bugs still or take longer and have it be more solid. There will always be bugs but the balance of timing and number/size of bugs is the hard part.

Why can't we have it both ways? Quick release with a stable product?

Maybe Apple just needs to put effort into it (resources, focus, etc.)

Tim talks about Apple making the best products being their focus. Well it needs good hardware and good software to do that. The development of these things need people making them.

I just think Apple needs more quality people to make quality products.

Things like this make me think that Apple is slowly letting things die. It worries me about their future, and stock prices, and products for me to use.

I think they need more of that underdog fight or die attitude they had right around the time the iPod was released.
 
Easy guys we will releasing in the coming weeks.We have a lot of work to do and we have some pleasant surprise for you on 10.8.3 Build.

That is not what you said the other day.

I'M excited about the 10.8.3 update that is coming out! Can you please tell me when! I am pressing the software update button 10 times a day trying to get the update. Please! When?
 
Are you really an Apple developer? If you are, prove it.

I think you missed the 'Baghdad Bob' image under his statement (i.e. he was joking).

Actually I want to know if they fixed the annoying notifications calendar issue and the ability to pick a 'snooze' duration.
 
The bugs will still be there.

Of course there will always be some bugs, but that's missing the whole point.

The reason you keep doing more betas is to get more things fixed. Not to get everything fixed, to get more things fixed.

With any bug fixing process, the balance is always between updates more often with fewer fixes, and updates less often with more fixes. These continued betas simply mean that they have a goal of fixing certain (and enough) things, and they don't feel like those things are fixed to their satisfaction.


Why can't we have it both ways? Quick release with a stable product?

Because some things simply take time, and throwing more resources at it doesn't always help. I guess you've never heard the cliché about getting nine women together to produce a baby in one month.
 
Having recently switched over from a PC to a Mac, I'm finding it hilarious how everyone's life is put on hold for an update. I always heard that Apple fans were sheep, but I never dreamed it was this bad. Here's an idea, go outside, get some sunshine, and whenever the update is ready they will release it.
 
Does my response to this post show I care ?

thinkaboutit.

;)


If you respond to any post it shows you have some interest otherwise you wouldn't bother.

The irony that i see is that i'm pointing it out and i care, I certainly wouldn't waste good time arguing if i didn't lol.
 
Craig Federighi took over OSX at Apple about when 10.8.2 was released.
I am told by people within Apple that he has an engineer's mindset and has been very disappointed with the stream of minor bugs and irritations that built up within Lion and Mountain Lion.

This long delay with 10.8.3 may (let's hope so) confirm this.
It would be nice to believe that, every week, he tries the latest 10.8.3 then comes into the engineering meeting screaming "Does it fix the power management bugs? NO! Does it fix the locationd crashing bugs? NO! Does it fix the Finder caching and displaying out of date information bugs? NO! So go and fscking fix them. Because no way are we EVER shipping again a piece of software as buggy as we have over the past eighteen months --- not as long as I am in charge!"

Good old school management is required when empowered employees screw one after another. Trust is gained and lost Applebes.
 
Having recently switched over from a PC to a Mac, I'm finding it hilarious how everyone's life is put on hold for an update. I always heard that Apple fans were sheep, but I never dreamed it was this bad. Here's an idea, go outside, get some sunshine, and whenever the update is ready they will release it.

That's the same sorta behaviour for fanboys of all stripes.

Microsoft doesn't encounter this sorta problem only because the update train rolls into the station the second Tuesday of each month, on schedule.
 
There has to be something more to it. I reckon there are some big internal arguments going on.

Or it could just be that now that Johnny Ive is in charge he wants patches and releases to be far more polished before they go public?

----------

I agree! Why didn't they just release 10.8.3 without fixes? I mean, it is just an updated name, it doesn't actually contain anything that needs time to get fixed - It is so unrealistic!

Perhaps they want to release the new Mac Pros imminently and 10.8.3 needs to be loaded onto it? That would mean they better smooth out 10.8.3 instead of having to rely on working on a new 10.8.4 immediately to fix issues with these new systems?
 
It's not about Apple releasing the update sooner or later, it's about how many engineers they're putting behind OS X compared to iOS because that's what the quality and frequency of the OS X updates depends on.

And how many engineers do they really have behind OS X? That, nobody can really tell us. ;)
 
Craig Federighi took over OSX at Apple about when 10.8.2 was released. "

He's been in charge of OS X for over 2 years. He took over iOS when Forstall left.

You would think "people within Apple" would know that!
 
Wow. I've been involved with Apple for a while, and I've never seen a beta take quite this long. I sure hope Apple's doing it to clean up old bugs that were never fixed, as I have some pet peeve bugs that have been around since Lion. ;)
 
Having recently switched over from a PC to a Mac, I'm finding it hilarious how everyone's life is put on hold for an update. I always heard that Apple fans were sheep, but I never dreamed it was this bad. Here's an idea, go outside, get some sunshine, and whenever the update is ready they will release it.

This is a little too simplistic. Let's be a little more nuanced shall we. Many of us long time Apple users have become accustomed to having very stable and reliable software that works seamlessly with the hardware. However, for some of us, the hardware we purchased in the summer didn't run very efficiently with current software, and since the software is now going to be released on an annual cycle, is the new status quo going to be that we only get roughly 3 months of stability? 10.9.3 or 10.9.4 only to come out 3 months before 10.10?

If they speed up the release cycle to an annual one for OS X, I don't think it's unreasonable to expect that the major kinks should be ironed out on a faster time scale too. Fixing things at the old rate is no longer as acceptable for a premium product given the new release cycles. There should be a better balance.
 
Some people really need to get a life. Apple can do betas as often as they want to. They will release it when it's ready.
Uh... no, they can't.

If something new is broken in 10.8.3 (or they fail to fix something they've known about), do you really think folks are going to wait around for the next 13 rounds of betas before it's fixed?

The longer this takes, the higher the expectations and Apple is setting themselves up for a big fail if they don't meet those expectations. I'd just as soon see them whittle down the bugs bit-by-bit with more frequent updates. At least you'd get "some" of the benefits of those few things that have most likely been fixed since version 2 or 3 of the beta.

The more I think about it the more it sounds like this is the last update we'll ever get before 10.9. (Unless it's about Java :D).
 
Because some things simply take time, and throwing more resources at it doesn't always help. I guess you've never heard the cliché about getting nine women together to produce a baby in one month.

You are right to a degree but in this regard I would venture it is a small degree. If they had more programmers working on it they would probably develop it faster. If I clean my kitchen it takes me longer than if my whole family cleans my kitchen. I think programming is closer to cleaning a kitchen then it is to producing a baby.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.