Separate names with a comma.
Discussion in 'Mac Pro' started by tony3d, Jun 4, 2012.
Just thought I'd beet everybody to it. LOL.
It's down all right, but I can't see anything major happening before the Keynotes....Mind you, it is Apple we are talking about here...Maybe they will release updates beforehand...( I doubt it)...
I'm surely there're no product update at this time!!!
I spell it wrong all the time...
I imagine a lot of back end updates before the major overhaul that will be next Monday. Back in the G4 era it seemed that as soon as Steve finished his "one more thing" the store was back up, these days they propagate after several hours until the servers seem to settle. Hopefully they will really just have to 'flip the switch' when all the new announcements are officially public.
With the recent rumors of a Mac update bonanza at WWDC, if they're going to update it, it's probably going to be at WWDC.
Part of me wonders if they're not going to try to sync all their Macs to the same revision date.
Makes sense, it worked with the release of the new iPad, and the IOS update...As soon as the keynote was done, everything went live...Considering the amount of updates and changes that are rumoured this time, a lot of work will need to be done behind the scenes on the servers to get them ready....I'm not in my update year, so will watch the new stuff with interest, but won't be buying this year.
Would be cool to get a mammoth update - especially as they've not introduced any in Q1. Would be perfect time for a refresh at the launch of OSx Mountain Lion.
Seems to be up in US and UK.
I sure hope so. How bad are we going to feel if all the others pop (as has been suggested by 9to5 today, and still no Mac Pro? That would be a kick in the stomach direct from Apple.
Unlikely. This has been driven in part by SNAFUs by Intel and TSMC ( NVidia and AMD). It is not likely they will all slide again into the same volume shipping dates again.
This whole "Mac Big Bang" release smells much more of the rumor sites doing shotgun blasts in order to hit the broad side of a barn. It is probably great for page views. Every "submarket" of the rumor circles are all hitting your site because every single Mac model with a fan following is going to read the article.
With OS X going to a 12 month release cycle this would be a bonehead cycle to get into. One month (or two ) before the OS X is to update .... release a whole Mac line up with the "soon to be retired" OS on it. Anyone think that makes sense?
If the news is true about a batch of updates for next week then maybe Apple are preparing the site in terms of server overload or stress testing.
Can you imagine how mad it will be if the products will be available the same day as the announcements.
you should be red as a beetroot from shame for posting this !
After the pundent comments last week, I feel pretty confident in the Mac Pro sticking around. But I could see no Mac Pro update at WWDC causing panic.
It's not down here?
It was down about 12 hours ago for a short time.
3 of the 4 Macs I have bought in the last five years have come with an update for a new OS (separate install disk) or with my last a free download of Lion. I don't really think Apple cares if the OS and new hardware are synchronized.
That isn't the point. Some of those Macs could have been initially released 6 months before. It isn't the "cost of discount Upgrade disks" that is the issue. That are just worth the cost just to avoid the "Osborne Effect" costs if strongly motivate people to defer purchases for a long time for a pre-announced product.
Each new Mac typically comes with a new version of Mac OS X or at least some driver updates. So 10.7.4 and Macs with major new hardware show up and 10.7.5 drops.
The "cost" that Apple be motivated to avoid is issuing a x.y.(n+1) update that will exist a totally of a couple of a weeks. It is waste of time creating that than if just waited another weeks and entirely skipped major components of (n+1) update all together. [ some parts of a n+1 update will be critical bug fixes ]
The cost is even more apparent if that new drivers for the n+1 update have bugs in them. If need to update both x.y.(n+1) and x.(y+1).n with bug fixes. The development and QA processes are more expensive both of those than if just dropped an update for x.(y+1).n .