I'm going to just leave it on my M1 Macbook Pro this year. Nowhere else. Photoshop is completely borked when trying to run in the current developer beta. Not surprising at all I suppose. But it took me a bit of time to figure out what was happening.
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.
macOS Tahoe Public Beta Available for Some Users [Update: Pulled]
- Thread starter MacRumors
- Start date
- Sort by reaction score
Federighi looked like he was walked on thin ice in that recent post wwdc interview with Joz by his side
But apparently nothing ever happens
He’s charasmatic but his legacy for software quality control stinks
I wonder how quickly third party developers will adopt the design. It's also really hard to get into test flights for a lot of apps, otherwise I'd run them and report feedback :\
A lot of the built in system stuff (navigation bar / tab bar backgrounds, button backgrounds, etc.) will adopt it by default, there are glass APIs for both SwiftUI and UIKit to customize your own in app stuff.
Still kinda surprised they put the 26 all the way after the Tahoe.
Should optimally be macOS 26 Tahoe. (The Tahoe is actually just a marketing thing and for ID purposes harder to remember and relate to for most people, so it is kind of an irrelevant Dunsel except to Apple Marketing).
Should optimally be macOS 26 Tahoe. (The Tahoe is actually just a marketing thing and for ID purposes harder to remember and relate to for most people, so it is kind of an irrelevant Dunsel except to Apple Marketing).
Was the perfect yes man for partnering with Ives. Craig was at Next with Steve, so I won’t question his engineering skills, but not all star players are born leaders. The number of pulled updates is laughable, and are a regular occurrence. Cook doesn’t have what it takes to right this ship.
I don't think the software quality control is his fault. I think that marketing is driving the ship at it comes at a detriment to the engineering. Anyone who has actually done real software engineering knows that software is ready when it's ready, not when marketing says go. The way releases work at Apple these days, marketing pushes the button to release. It doesn't really matter if it's ready or not. This is evident in hardware just as much as software. Exactly what Steve did NOT want to happen is happening, but even worse. Steve famously once said they would ship it when it's ready. He also famously talked about Intel being problematic because Apple became bound to Intel's release timeline, not its own. Now, they've become bound to their marketing team's timeline. The next iPhone will launch in September because the marketing team says so - not because that's when a newer, better, greater iPhone can/will be ready. Imagine the improvements (innovation?) that could happen if the hardware teams could design around what they want to build rather than what they can build in the allotted time. Imagine the software bugs that could be squashed if they just had an extra 90 days this year. Well, marketing is pushing the button ready or not.
Bit of a harsh assumption, no? Why not both? If I weren’t writing a PhD thesis in a hurry right now, I’d wipe one of my multiple external SSDs just to take a gander at Tahoe at the earliest possible opportunity, and me not being a developer, that would be public beta 1, of course. And, as per usual, I’d be constantly firing up Feedback Assistant to file reports of all kinds (including suggestions, yes, but most importantly, bug reports and diagnostic data). Can you safely assume that our fellow forum member didn’t do that for each and every one of those bugs?
You nailed it. Apple Intelligence is another shining example of “PR says it will release on XYZ date, so it will release on XYZ date.”
Yes that’s part of the issue but when something bricks devices and you have a growing perception that you are behind in software, that’s just making marketing around it worse. There are issues that transcend the release dates and never see proper fixes. .1 releases that brick certain models or cause new issues. It’s a combination of things, but Craig is more marketing than substance in results. So he doesn’t deserve an easy pass all these years later.
Now with everything cemented by name attached to the calendar year, things aren’t going get much better.
Tahoe is a mess. The glass reskin was slapped onto the OS with no thought. First, you barely notice the fancy glass effects. Second, you have blurriness between the glass elements that makes no sense anymore (-> reskin no redesign). Third, Spotlight is still completely buggy and we are in Beta 3 already.
I don’t think this was much different under Jobs.
if anything, it was worse, because the updates were significantly bigger.
I know for a fact that there are archived articles of the initial release of 10.4.0 Tiger breaking tuns of applications, same was true with leopard and snow leopard.
not to mention the disastrous launch of mobile me, iOS 4 was extremely rough (and took an additional six months to arrive on the iPad), and this isn’t even to mention the first two initial releases of Mac OS X, Chita and Puma, which everyone at the time agreed we’re not ready for public use, including Apple themselves.
It doesn’t have to be super polished. It can basically a first draft. Basically all you are doing is to get feedbacks from beta users and go from there, and keep developing till final release of iOS 26.
I will say our app... doesn't look great with liquid glass. not terrible but LG is all about scrolling content, but if your app doesn't scroll it looks wonky and cluttered
Spoke too soon
Wednesday.
Dev Betas are released first and then Public Betas the day after.