Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Targeting Late October for OS X Mavericks Launch
- Thread starter MacRumors
- Start date
- Sort by reaction score
No, we are not joking. The icons in Mavericks will be big, round, colorful balloons to match the style and motif of iOS 7.
Yeah, you've made your point. Thanks. And I still don't think you know what sarcasm is. Or perhaps you require "/s" markup to be certain.
How about we drop it so the thread doesn't get even more derailed and so the mods don't get all worked up, eh?
UPDATE: iBug claimed I referenced the time between each official 10.x GM/public release and the next 10.x WWDC announcement, while I listed development between the WWDC announcement through the GM/public release.
Post 180:
Again, I did NOT reference 10.x.x updates, only 10.X - GM releases. This has nothing to do with incremental updates. Reading comprehension is a good thing.
Just to clarify, I reference ADC development releases and not in-house development as we do not know when 10.X updates begin development aside from build numbers, which still don't list dates. No one aside from Apple engineers knows exactly when in-house development begins before each 10.X ADC release.
To understand why this matter is relevant requires a knowledge of Apple's OS X development, Jobs' structuring of engineering, effects [positive and negative] on iOS and OS X development and AAPL stock. It is a simple solution to an unnecessary complicated matter.
The launch of Apple's iPhone was an unprecedented global campaign for Apple, as such much was riding on its release. The small Apple engineering department was unable to keep pace with both OS X and iOS development. In 2007 Leopard was delayed as iOS engineering was exhausted:
After the delayed release of 10.5 "Leopard" in 2007 due to iOS development, "official" OS X launch dates became less specific [perhaps to allow developmental leeway]. This doesn't excuse the reality that delays could be avoided (I'll explain below).
Jobs was notorious for demanding a small team of engineers; his insistence on knowing the engineering base allowed proper direct involvement in projects and to determine whether or not an employee was a proper fit; "tight control" impossible with a larger workforce. However this comes at a price.
Apple could satisfy both matters while avoiding delays and [by-proxy] producing more stable OS X releases. Build out the engineering departments; dedicate iOS and OS X team "sections" while maintaining an iOS and OS X cross engineering team. This may allow iOS releases to "stay on course" with iDevices launches without moving engineers from OS X.
Think in terms of workflow. On the left place iOS development, on the right OS X, in the middle all Apple engineers. Since the iPhone launch, OS X engineers are almost always moved to iOS development further stressing a thin engineering base. In normal business circumstances this would be unacceptable. Project managers and department heads would be held accountable and action taken to avoid this from reoccurring. Apple has grown tremendously since 2006-2007, yet their engineering teams haven't matched market growth resulting in a game of chess, further stressing a thinly spread engineering team and resulting in delays (even with vague launch frames).
You may be asking yourself how I know any of this as "fact". This requires a bit of OS X history and some personal knowledge via friends at Apple.
OS X Development
10.1 Puma: Announced July 18, 2001 , GM/public release September 25, 2001 [3 months of development]
10.2 Jaguar: Announced May 6, 2002, GM/public release August 24, 2002 [4 months of development]
10.3 Panther: Announced June 23, 2003, GM/public release October 24, 2003 [5 months of development]
10.4 "Tiger": Announced May 4th, 2004, GM/public release April 29th, 2005 [11 months of development]
10.5 "Leopard": Announced June 26, 2006, GM/public release October 26, 2007 [16 months of development]
10.6 "Snow Leopard": Announced June 9th, 2008, released August 28th, 2009 [14 months of development]
10.7 "Lion": Announced on October 20th, 2010 and released July 20th, 2011 [9 months of development]
10.8 "Mountain Lion": Announced February 16, 2012, GM/public release July 25, 2012 [6 months of development]
10.9 "Mavericks": Announced June 10, 2013, on track for ~ Oct. 2013 release [current ~5 month estimate of development]
Delays:
2007
- Apple delays Leopard release until October
- Apple Delays OSX Leopard
- Mac OS X 10.5 Leopard Delayed until October?[/CENTER]
2009
-
Apple's Snow Leopard may be delayed - analyst
- Snow Leopard support delayed a few weeks
2013
- Apple hijacks OS X devs to keep iOS on track
A few friends who have worked for Apple in various departments; design consultants on Pro-Apps, engineers, marketing, even interns, are either leaving or considering leaving as the atmosphere hasn't improved. From what I understand Apple engineering departments are exhausted. The bittersweet pill after Steve Jobs' passing was the hope CEO Tim Cook would [finally] approve the hiring of more skilled engineers to alleviate the stress and tension between iOS and OS X development. Firing Scott Forstall gave many hope that it may bridge the [now known] divide. Many now seem less optimistic. Product demand and project managers under Cook are taking advantage of Jobs' absence [as stated by a few I know]. Instead of proper department oversight, project/department heads aren't directly involved but rather "lead" from afar.
The misbelief that hiring more is merely pouring gasoline on the fire isn't entirely true. Proper departmental re-evaluation is sorely needed. Determine which departments require more support and recruit new hires within restructured departments. Simple business strategy. Firing SVP's without any replacements [or inadequate hires] and placing control to already strained department heads (Ive's for example) isn't the solution, it merely stresses an already weakened system.
Apple would benefit from re-evaluating departments, determine which area's require more focus based on the current market and future projections, hire adequate retail and engineering department heads, improve software development, retail strength, product focus and updates, and revisit the marketing campaigns that brought so much [positive] attention to Apple's products.
- Snow Leopard support delayed a few weeks
2013
- Apple hijacks OS X devs to keep iOS on track
A few friends who have worked for Apple in various departments; design consultants on Pro-Apps, engineers, marketing, even interns, are either leaving or considering leaving as the atmosphere hasn't improved. From what I understand Apple engineering departments are exhausted. The bittersweet pill after Steve Jobs' passing was the hope CEO Tim Cook would [finally] approve the hiring of more skilled engineers to alleviate the stress and tension between iOS and OS X development. Firing Scott Forstall gave many hope that it may bridge the [now known] divide. Many now seem less optimistic. Product demand and project managers under Cook are taking advantage of Jobs' absence [as stated by a few I know]. Instead of proper department oversight, project/department heads aren't directly involved but rather "lead" from afar.
The misbelief that hiring more is merely pouring gasoline on the fire isn't entirely true. Proper departmental re-evaluation is sorely needed. Determine which departments require more support and recruit new hires within restructured departments. Simple business strategy. Firing SVP's without any replacements [or inadequate hires] and placing control to already strained department heads (Ive's for example) isn't the solution, it merely stresses an already weakened system.
Apple would benefit from re-evaluating departments, determine which area's require more focus based on the current market and future projections, hire adequate retail and engineering department heads, improve software development, retail strength, product focus and updates, and revisit the marketing campaigns that brought so much [positive] attention to Apple's products.
Last edited:
First: Apple always said "fall", which exactly is in october. What delay are you talking about?
Second: Rumors from stupid bloggers and internal Apple goals are totally different things. Maybe (and I'm pretty sure) they never intended to do an iPhone AND iPad event.
Third and most important: What features in OSX are you missing right now? Is it unusable for you?
So what are you talking about? You only wrote nonsense and used wrong terminology.
So now Mac OSX takes second place to iOS.
To state that it enables more focus on iOS is laughable, are they assuming we believe the engineers that work on OSX work on iOS, yeah right...
The focus of Apple has moved from there base to iOS devices, and instead of keeping both products on an even keel, they have swayed towards iOS, leaving Mac users picking up crumbs.
Geez even Mac Rumours has moved on, now has Samsung and Android news!
To state that it enables more focus on iOS is laughable, are they assuming we believe the engineers that work on OSX work on iOS, yeah right...
The focus of Apple has moved from there base to iOS devices, and instead of keeping both products on an even keel, they have swayed towards iOS, leaving Mac users picking up crumbs.
Geez even Mac Rumours has moved on, now has Samsung and Android news!
Hell hath no furry like an internet form poster scorned.
Let's just drop it, ok? I don't want to play any more.
You all win. Collect one internet. You right. Me wrong. Happy now?
Jim has sources in Apple and has never been wrong (AFAIK) when confirming or denying Apple rumors. And he seems like a pretty good guy, unlike some people.
I'm looking forward to installing this on my PowerBook G4 and Color Classic and 128k. Can't wait.
I hear the new chooser looks great.
I hear the new chooser looks great.
Last edited:
I'm sure that Apple is already hard at work on 10.9.1 - it's only good engineering practice.
My Mac Mini Pro agrees with you - oh wait, it doesn't because I don't have it yet. It's vaporware.
Apple doesn't want you to have RAM slots - you might upgrade your old Apple after a year instead of buying a new Apple.
LOL - you understand the upgrade dilemma....
iPhone and iPad are Apple's moneymakers in this era, so Apple puts iOS as #1 priority.
That leaves the Macintosh shelved as side project, lower priority, on the backburner.
What a sad time it is for a MacAddict!
That leaves the Macintosh shelved as side project, lower priority, on the backburner.
What a sad time it is for a MacAddict!
I completely agree with you but:
1) iOS devices, especially the iPhone make huge profit margins (costs $200 to make, sells for $700). Also, iPhones are upgraded more often, as majority of cell phone contracts are only 2 year long and so is the iPad, as compared to Mac, which I've been using for 4 years with satisfaction. Basically, iOS gives them, higher profit margins and also higher quantities of sale, year by year.
2) iOS vs Google's Android competition is much more intense because Google is actually a innovative company and is a serious threat to Apple, whereas Microsoft's Windows 8 Operating systems are a joke compared to OS X (however, software compatibility is another issue). Microsoft just can't get it right, they're confused and are confusing their customers.
The first reason is common sense, but the competition from Google's innovation is a serious concern for Apple. Microsoft ... they're still looking for the right guy to run the company.
Last edited:
I agree, but actually when you compare an Apple computer with a similar PC, then you will be surprised to find out that the Apple products are actually cheaper! Just compare a Samsung ultra notebook to a similarly configured MacBook Air.
Apple just doesn't produce low budget computers. You won't find an Apple computer for 400$ in the supermarket. This is how the Windows industry has grown. Many people don't want a high end computer, they just want to have something that can do the job and doesn't cost a fortune. That's why PCs have taken most of the market share.
I think the same is happening with iOS too, but this time Apple seems to be reacting by creating a low budget alternative.
1 more, and then GM the first week of October, so public release can be around 2.5 weeks after the GM, exactly like Mountain Lion.
No it's not. It's announced 3 months ago, they said it'd ship in 2013, we are not in 2014 yet. So it's not vaporware.