Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS Tahoe

apple.com

Post reply on HN
Print view View original

931–940 of 1001 posts

Re: macOS Tahoe

#931

Post by roody15 »

Email I sent to staff

Good Afternoon,

Apple released its new operating system today, macOS Tahoe. This is a full version upgrade (26.0) with a new look, feel, and many changes. At this time, I recommend NOT updating to Tahoe for the following reasons:

Stability: Version 26.0 is the first release and, like most “.0” versions, contains glitches that will take time to fix. Later versions (26.1, 26.2, etc.) are expected to address these issues.

Release Cycle: Apple now releases a new macOS every year instead of every two years. These initial yearly releases are often closer to “beta” products, and Apple typically patches problems over the first 6–8 weeks.

There is no real advantage to upgrading right now. It’s best to wait 6–8 weeks until the system stabilizes and then reevaluate.

How to Skip the Upgrade

When prompted, simply do not click “Upgrade Now.” This upgrade may pop up on your machine over the course of the next few days.

Close the upgrade window, or scroll down to select other updates.

For reference, macOS Sequoia (15.x) is now at version 15.7, which means it’s very stable and well-patched.

Re: macOS Tahoe

#932

Post by fair_enough »

fair_enough wrote: post #122

Shwiggity shwagg, the GA release hath come! Can't wait to write a beamline control application for crystallography on this sumbitch!

Whoever downvoted this despite the fact that it was neither factually inaccurate nor disrespectful to another person, congrats on being an incel.

P.S. My hot Japanese fiancee thinks you're pathetic too. Her exact words were: チー牛

Re: macOS Tahoe

#933

Post by ryandrake »

cosmic_cheese wrote: post #909
AlexandrB wrote: post #898

Earlier quoted context omitted.

You can't blame this all on backwards compatibility. Microsoft can't just stick to one successor technology and keeps obsoleting every attempt after a few years. With that approach, of course no one is going to move over.

That’s one issue, but another is that they don’t make into successors full replacements. They’ve stuck to WinAppSDK aka WinUI for a while now, but it’s missing such basic elements as a datagrid/tableview which makes it difficult to take seriously as a desktop UI framework.

Also, they didn't even migrate their own internal dialogs with each replacement. You can still uncover dialog styles all the way back to Windows 95-style if you poke around Windows 11 long enough. Whenever they came out with yet another successor, they haphazardly migrated a handful of P1 components and then called it a day.

Re: macOS Tahoe

#934

Post by caycep »

sbuk wrote: post #922
caycep wrote: post #869

Earlier quoted context omitted.

At least he was consistent and the UI design made sense, textures aside. And UI gossip aside, all the accounts from every engineer who worked under him consistently praised him. Safari with its KHTML underpinnings was also created under his watch, apparently.

Webkit (along with Safari) was started under Avie Tevanian's watch. Scott Forstall worked under him and Bertrand Serlet, along with Lisa Melton, who lead the development team for Webkit. Forstall was responsible for the development and release of Apple Maps .

I'm pretty sure Melton credited Forstall with giving with the support and cover for safari/khtml - she's written extensively about it.

https://donmelton.com/2013/01/10/safari-is-released-to-the-w...

And for Apple Maps, I remember reading somewhere that one reason Forstall refused to sign the infamous apology letter was that the initial release was from a team not directly under his supervision, but I can't find the old reference to that...granted, whatever went down was probably a joint failure of everyone involved

Re: macOS Tahoe

#936

Post by filchermcurr »

I'm trying to give it a chance but it's kind of rough.

- File save dialog has a massively reduced width sidebar. It has a resize handle. But the resize handle does nothing. This is the most infuriating thing for me because all of my sidebar locations are cut off. - M4 Pro Macbook Pro and I'm now experiencing stuttering when scrolling. - Why is everything in Spotlight enormous?! Was it always like this and I just seemingly never noticed?

Otherwise, if you 'reduce transparency' and turn off 'tint window background with wallpaper color' (both of which I had done already anyway), things are decidedly nicer visually.

Re: macOS Tahoe

#937

Post by awesome_dude »

ohdeargodno wrote: post #480
treesknees wrote: post #332

Earlier quoted context omitted.

Why not run it natively with Asahi Linux?

Asahi is only supporting M1, and partly M2 I believe. M3 was enough of a change that there are no drivers for it.

I run asahi on my M2 mini as the primary OS.

There's a bit of a pain in that I could only get Brave to run Netflix, but all that meant was that I switched to using Brave for all of my browsing.

There's no official Tor build for it, but there is an unofficial one (that I do not use)

The only real pain I have with it is that Facebook's javascript for its reels chews up RAM something horrible, which freezes the OS whilst being processed, and often causes me to reboot it

Re: macOS Tahoe

#938

Post by awesome_dude »

neobrain wrote: post #726
crossroadsguy wrote: post #461

Earlier quoted context omitted.

Is Asahi installed side by side on a mac? You pick it at boot? And how “install and just use” it is?

> Is Asahi installed side by side on a mac? Yes, the installer automatically (and reliably) resizes partitions for you. A minimum of about 70 GB for macOS is needed (anything lower is still possible but unsupported). > You pick it at boot? There's a default choice that will boot. > And how “install and just use” it is? Probably one of the smoothest Linux installs I've had in 10 years or so, since you just run the ins…

Just, FTR, you can also tell the Mac OS to reboot to Asahi, and you can tell Asahi (via CLI) to reboot to Mac OS

https://www.reddit.com/r/AsahiLinux/comments/1c2yasr/can_i_b...

When I was first getting my feet wet with Asahi I was using these methods a lot.

Re: macOS Tahoe

#939

Post by major505 »

user34283 wrote: post #930
major505 wrote: post #785

Earlier quoted context omitted.

Just curious, what yype of featureres where removed? To be honest Im new to macos, but after spending years suffering with gnome, that did removed a lot of features, Macos seens like it dosent suffer of this that much.

My mouse and keyboard are connected via the USB dock function of my monitor. After the update, I can't even login. Great. Not that it was working well before. To get the second monitor to even turn on, I had to first power off and then subsequently turn on again the primary monitor. And that ritual was unique to my M2 Pro Mac mini. On Windows, or a M1 Pro Macbook, everything just works. And I'm not the only one with…

yea, same thing here. I have the M1 Pro MacBook, connected via usb-c hub. No bugs so far.

Re: macOS Tahoe

#940

Post by p_ing »

dijit wrote: post #915
hulitu wrote: post #879

Earlier quoted context omitted.

> because we have a significantly better baseline for how computers are actually used. Except, they don't. X was device agnostic. Wayland makes some asumptions which will be wrong in 10 years. And being a monolith does not help.

this "device-agnosticism" is also the source of many of X11's modern problems. Because the X server has to handle all rendering and input, it acts as a middleman. For every frame, an application has to send rendering commands to the X server, which then composites the scene and sends it to the display. This extra step introduces latency and makes it difficult to implement modern features like smooth animations, varia…

> introduces latency and makes it difficult to implement modern features like smooth animations,

Move X [Wayland] into kernel space [provided stability isn't a concern].

It's easy to type that out, of course.

Post reply on HN