Mountain Lion

[Steve Connor]

[Bill Davis] “Well, yes. When it’s a company like Adobe that actually ships what they promise around when they promise it.
“

Which is exactly what Apple did with Multicam and external monitoring

Steve Connor
“FCPX Agitator”
Adrenalin Television

[Steve Connor]

https://www.macrumors.com/2012/02/16/apple-officially-drops-mac-name-from-os-x-mountain-lion/

Steve Connor
“FCPX Agitator”
Adrenalin Television

[Rafael Amador]

[Andrew Richards] “If Apple is committing to an annual rev on OS X, even if they are more evolutionary revs, this is a stake in the ground that augurs well.”
New bugs, new incompatibilities, new drivers every year.
Is it really necessary a new system every year?
rafael

http://www.nagavideo.com

[Brad Davis]

Get ready for the Mac Pro refresh…

https://www.mactrast.com/2012/02/mountain-lion-will-not-support-older-graphics-chips/

[Andrew Richards]

It might be a bit more work for third parties to stay current, but the alternative is what happened with Windows XP where hardly anything changed for almost a decade. My observation is Apple has turned a corner with their Core frameworks where they have shed much of their legacy tech and can move forward additively rather than desruptively. So much of the guts in Lion is brand new or still very young code compared to stuff like QuickTime which dates back decades. That is not to say there won’t be version dependency issues, but the bad old days of brittle dependencies on stuff like QuickTime are behind us. They still have legacy left to shake off (HFS+ is as old as the Mac itself!), andI’m just glad to see a commitment to the desktop that matches the effort they are putting into iOS.

Best,
Andy

[Marvin Holdman]

“And then the reveal: Mac OS X — sorry, OS X — is going on an iOS-esque one-major-update-per-year development schedule. ”

Anyone else who’s been doing this a while notice that it’s becoming more and more difficult to manage keeping a facilities systems updated as these cycles continue to come with greater and greater frequency? I’m not sure whether it’s by design, or default, but it seems that software purchases are coming at more frequent rates these days. The discussion with our IT department these days is about trying to decide whether it’s better to only upgrade when new features are absolutely needed, or to try and keep up with them as they come. On one hand, you can save short term funds by skipping upgrades and take a hit bringing a legacy system up to date, or you can take the incremental hits and pains of simply staying current as you go.

Did this statement spark any particular conversation in your world?

Marvin Holdman
Production Manager
Tourist Network
8317 Front Beach Rd, Suite 23
Panama City Beach, Fl
phone 850-234-2773 ext. 128
cell 850-585-9667
skype username – vidmarv

[T.a. Franks]

And with this is the end of the Mac coming?

What do you guys think?

[Jeremy Garchow]

[Marvin Holdman] “Did this statement spark any particular conversation in your world?”

I only upgrade when needed.

I finally setup two test drives with Lion after the Kona drivers required it for FCPX.

I will say, the upgrade to Lion was really easy. Just because the update is available doesn’t mean you have to install it.

Jeremy

[Marvin Holdman]

“I will say, the upgrade to Lion was really easy. Just because the update is available doesn’t mean you have to install it.” – Jeremy Garchow

Totally agree that OS updates have never been easier. Principally agree that you don’t have to install it. That being said, it seems like every upgrade we’ve taken recently has mucked up something. Usually, it’s more an annoyance than a crisis, but it still takes time. While we don’t upgrade immediately after a release, and usually take an incremental approach (test it on one machine and figure out the issues before full scale implementation). Lately we’ve been trying to keep our OS current.

My concern is holding off through multiple incremental upgrades until we have too do one (for whatever reason). How many annoyances are going to crop up when we skip, say 3 or 4 incremental upgrades? How are you going to troubleshoot when that happens? Which version would you go back too?

I certainly understand the benefits of more frequent release cycles, just trying to come up with a sound approach for coping. Continue incremental upgrades or only upgrade when absolutely necessary? The approach up to now has always been, upgrade only when necessary. Just questioning that approach as the industry seems to be changing.

Marvin Holdman
Production Manager
Tourist Network
8317 Front Beach Rd, Suite 23
Panama City Beach, Fl
phone 850-234-2773 ext. 128
cell 850-585-9667
skype username – vidmarv

[Jeremy Garchow]

[Marvin Holdman] “My concern is holding off through multiple incremental upgrades until we have too do one (for whatever reason). How many annoyances are going to crop up when we skip, say 3 or 4 incremental upgrades?”

I went from 10.6.7 to 10.7.3 on one computer. I didn’t really skip a beat. Sure, I had to update some drivers and such, but that’s OK and took a few minutes.

[Marvin Holdman] “Continue incremental upgrades or only upgrade when absolutely necessary? “

I think part of this will be driven by developers and how fast they can keep up.

Digital Rebellion just made an announcement that will gradually phase out support for 10.5/PPC moving forward, and are looking forward to the new updates in 10.8. It’s always good to hear positive things from developers, in my opinion: https://www.digitalrebellion.com/blog/posts/planned_deprecation_of_os_x_10.5_leopard.html

Jeremy