Any reason to start with Monterey?

[Killerbob]

I am getting my Mac Studio in a few weeks, and I am pondering if I even want to set it all up on Monterey... My Mac Pros are both running Monterey, and they are my working machines until the Mac Studio is all up and running all my software.

Knowing that macOS Ventura is in preview right now, and will move to public beta by the time I get my Mac Studio, I think I just may skip Monterey all together.

Anyone else running Ventura on their Mac Studio?

 

[lcubed]

stick with monterey until they work out the initial teething issues with ventura.

depending on how some of the third party software installers are setup, they might
refuse to install on ventura.

 

[wdhpgx]

I don't generally move to a new MacOS version until at least 6mo after release. So no, not running Ventura here.

 

[Killerbob]

And I am the other way, I have often put on the Beta 1 on even my working machines, and never had any significant issues that couldn't be solved. The vertual Thunderbolt host issues in Big Sur were a PITA, but I "just" switched to 10GbE to conenct to my NAS.

 

[lcubed]

if it's not a critical revenue producing production machine, go for it!

let us know what to avoid

 

[F-Train]

I'll run Ventura public beta on either my Mac Studio or on a 2018 Mac mini. For me, the main issue is third party applications that won't be cleared for use with Ventura for months. It will be a matter of which computer I want to run those apps on.

 

[solardudesf]

One reason you may not want to, if you use it, is that in Ventura they drop OpenDirectory server support completely now. May stay on Monterey until I find a suitable replacement.

 

[haralds]

Wait! A lot of things like Universal Control are not working right. Some software like most of the tools from Rogue Amoeba are not yet functional etc.
Apart from the questionable benefit of Stage Manager you do not gain much.
I have both running on my Mac Studio and stay mainly in Monterey.

 

[AlteMac]

I would not run a beta on a production machine. As noted, there are always issues with betas (if it was ready for prime time, it wouldnt be a beta). Some issues are solvable quickly, some not so quickly, especially with third party software and drivers. I've had scanners and printers orphaned by an OS update. Adobe is pretty good at keeping up -- but not always. Third parties offering filters or add-ons for PS or LR do not always stay current with betas. Better to wait for the official release if you rely on them.

 

[orionquest]

Sounds like a new shiny addiction.

 

[yukari]

I agree with @AlteMac and @Icubed, if you use the machine for work, then no. If not, then sure why not. I use all my Macs for work, and I will put beta of Monterey, because I know all the softwares I need for work are working. Even then, I would put one on beta until I see no problems, then I would put beta on other Macs.

 

[Killerbob]

I was just notified that my Mac Studio will be here two weeks early, which I reckon will be to early for the public beta - which is my trigger for putting it on my Macs.

As for production vs. fun machines, my nMP is my serious machine, and my 2013 MP is my fun machine. My production nMP is used for paid video and photography work, and my trash can for photo editing, but I will survive if it’s not working properly. The Mac Studio will replace my trash can, unless it proves faster than my nMP.

 

[bobcomer]

A beta OS on a brand new machine isn't a good idea. A new machine needs a break in period for you to know if it works correctly. Putting a beta OS onto an unknown machine is just asking for trouble and you wont be able to guess what the problem is.