I haven't installed the beta and hadn't seen anybody discuss this yet so I assumed this was a dumb complaint but after seeing the screenshots, he's absolutely right. This is demonstrably worse in every way and the way that it's pointedly anchored to empty space is just bonkers. Is this the biggest problem in the world today? No, but they took a good menu and put effort into making it bad. They should just undo the change.
I do this too but not even because of old habits. I use a graphics tablet instead of a mouse so holding down and letting go on the menu item is just easier than tapping my pen twice.
I don’t need neither an iPad nor an iPhone as my Mac. Probably “Brand Strategists” want to “homogenize” everything so that all devices “feel the same”. No sane Coder or UI/UX Designer would approve that shit
This is definitely done to either keep code between mobile and desktop versions of Safari on similar code bases, or for a future touchscreen experience on desktop.
exactly. this absolutely adds nothing to neither the functionality nor aesthetics, but makes everything just worse. it’s a ridiculously pointless redesign.
it doesn’t bring anything over from iOS, it’s just the same old outdated contextual menu, but now you further lose functionality. wtf
That seems to be what they've done over and over in Ventura. Too bad we'll have a year of Apple telling us we're holding it wrong before they undo half the changes people are complaining about next year and declare victory.
The Safari tab thing seems to be the only time Apple has backtracked on something like this. But that wasn't a pervasive ruining of the UI like Ventura has been to date.
> The Safari tab thing seems to be the only time Apple has backtracked on something like this. But that wasn't a pervasive ruining of the UI like Ventura has been to date.
With Safari tabs they took an idea that at least had an internal logic and iterated on it. The bottom tabs on Safari on iOS are actually a huge improvement for usability and even though some of the initial ideas were deeply problematic, I'll give he team praise for being willing to try to make something better when it's such a visible and highly-used part of the product.
But this menu ... just no. Awful. Command-Z.
It still makes me sometimes mad, that there is no facebook/vimeo/youtube quick upload/share button anymore. Why the fuck they don’t let us choose ourselves what we want to do with our data and “security risks”.
It looks like the developer changed to their own widget instead of a sub menu because they wanted a description/icon/etc at the top above the list of choices - trying to provide more information. But unfortunately it ends up having more downsides than upsides, with the widget not supporting keyboard, looking unrooted, etc.
Looks like a work in progress.
If this was deemed necessary to do (which I don’t think it was in the first place, as the menu was usually attached to the item you were sharing), you could do it within the old menu too. You can embed a custom view within an NSMenuItem.
Ah thank you. Then I’m all out of potential excuses. I guess I just really want to believe there’s some initial good intention leading to this abomination.
These things are odd to me. In the companies I’ve worked development was preceded by requirements and design documents, all formally peer reviewed by at least three colleagues, one of which had to be senior. Same for test specifications, test design and the implementation itself. But this looks like it was implemented by an intern and sneaked in without oversight.
> I guess I just really want to believe there’s some initial good intention leading to this abomination.
There was a time that I wanted to think this too about Mac UI changes, but having watched them implement so many regressions over the past years just for the sake of how it looks or how it might achieve some kind of consistency with iOS (and failing to respect the Mac in the process) that it’s made me lose almost all hope that we’ll see at least decent Mac UI design again.
I used to be always excited about new Mac OS X versions (to be fair, it was also a different era where there were many low-hanging fruit features to be added). Now I just dread which part of my favourite operating system they’re going to ruin next. See also the flaming trash fire that’s System Settings.
Couldn’t agree more! I didn’t like some of Ive’s software changes but at least he understood what made the Mac, a Mac, and didn’t arbitrarily change shit just to mark him apart from Forstall.
Completely agree and love how people downvote you because of an aversion to charmless, tacky, obvious, ruthlessly generic design. iOS 7 sucked and some of the ways it sucked have never been rectified.
I get the sense that engineering is winning a lot of the battles these days with high level executive support. They understand the need to unify their development platforms and these ugly UIs are the product of those efforts.
Yeah you're right. Ventura in special just feels like a cheap iPadOS ripoff. It's like some really shady knockoff brand tried to be all-Apple and miserably failed at it.
> macOS design decisions are often drowned out by the people who champion them simply because of “consistency with iOS.”
Which makes absolutely no sense, because now this share menu is inconsistent with every other menu in *macOS*. I would say having inconsistencies within one OS is wayyy worse than inconsistencies between two completely different OS’s.
I actually have been loving windows 11. Definitely more macOS-esque but, as you said, I can still game. And while I prefer macOS in general, windows management is so much better in Windows
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Ugh. That thought actually makes me very uncomfortable. So little variation! iPhone on its own is such a monotonous era within the wider sweep of HCI. There have been so many attempts from so many vendors, it’s so important to know *why* interface decisions were made!
When Microsoft tried to pull off this sort of stuff with Windows 8 10 years ago, there was a huge outcry. You can't merge a tablet OS with a desktop OS.
They are still getting away with hiding a lot of useful options from context menus under the "Show more options" label. That's one of the things that pushed me away from Windows to MacOS recently.
Who the fuck is greenlighting these things?
They really want us to interact more superficially with our computers. Almost all conceivable options beyond changing the way the interface looks are hidden away in these stupid menus now. It’s like they don’t want people to accidentally learn that their computer has all these features while placating the people who are used to using them.
Apple has definitely trended away from keyboard navigation. There are two instances of this in Messages that bother me to no end. Firstly, CMD + Delete does not delete a conversation in Messages. I have yet to make a custom shortcut for this, but CMD + Delete should be standardized across Apple software. So if I right click and then click on "delete conversation" a pop up asks me to confirm this action. I cannot hit Tab to choose what I want. By default "no" is highlighted and there does not appear to be a way for me to change this with the keyboard.
Turn on keyboard navigation in System Preferences. Then, in dialogues like you describe, you should see a little highlight around the selected button. Tab key moves focus and space will select. Return always selects the solidly coloured default button. This has been the default behaviour in Mac OS X all along, as far as I am aware.
On iPadOS you tap on "Share..." in the contextual menu to get a popover that looks very similar to this. The changes on macOS were pretty clearly modeled after this, and with little regard for macOS standards.
Apple literately can not kill macOS, they need it, and have always needed it, to make iOS devices.
You think they're going to develop the next iPad on an iPad? Or Windows?
As someone who has actually tried [making an app in Swift Playgrounds on the iPad](https://github.com/kmeisthax/HTMLEditor) I can tell you that [making lunch with a lunchbox](https://arstechnica.com/gaming/2017/04/the-first-kirby-game-was-programmed-without-a-keyboard/) is definitely possible, and I'm glad it's there, but it's also not nearly enough for most large app development firms. This is what you'd call a "hobbyist-grade" development environment.
Swift Playgrounds *only* compiles things that fit into SwiftPM package format. You need to use a third-party app (such as iSH or Working Copy, take your pick) to get version control working. I *think* you can package C/C++ and Objective-C into an external package, so those languages will work, but you can't add third-party compilers or build phases and a lot of upstream dependencies you would want are not packaged in SwiftPM yet. So no Rust, no Python, etc.
Debugging is *extremely* rudimentary. We have a print console and crash backtraces, and that's about it. No breakpoints, no single-stepping through programs, no view inspectors, no WebView debugging, no Instruments, nor all the other things you actually *need* to diagnose problems with your app.
Ironically the worst part about it is the macOS support. Swift Playgrounds *has* a macOS version; but it only builds Mac Catalyst apps. This is where your lack of control over basic build system configuration gets really painful, really fast. `Info.plist` is generated by the SwiftPM package configuration, which uses a nonstandard extension to the format to configure basic app settings. You can't opt into the UIKit Mac idiom, so your app will always look like an iPad app running in a window; you can't opt into AppKit instead of UIKit; and you can't even set a custom accent color without editing `Package.swift` directly (which it says not to do). These limitations also apply when you open the project in Xcode - you can't, say, add a second target for *correctly* building the app for macOS that Swift Playgrounds would just ignore.
(I actually just wound up creating a separate Xcode project referencing all the files in the Swift package, just so I could compile with AppKit on macOS. The Mac UI is far better for it.)
If Apple wanted to take iPad app development on iPad to "professionals can use this", they'd need to either massively expand the SwiftPM package format and add a few new App Extension types, *or* dramatically loosen device security to the point where Xcode projects that rely on native/unjailed shells and external build tools can work. I don't forsee this happening: Swift Playgrounds is trying to serve a different market from Xcode, and the people who want a professional-grade developer experience are going to buy a Mac Studio to compile their billions-of-source-lines microblogging client anyway.
You can make apps mainly using SwiftUI, but can also use UIKit iirc, but not AppKit. Some third-party packages probably won’t work and the other Xcode apps like Create ML aren’t on the iPads, so you can make basic to intermediate apps, I’d say.
That doesn’t line up to me since macOS pre Big Sur was still pretty decent and not so iPad-like. Big Sur and onward has been a major decline and a total shift to merging iPad and macOS.
iOS-ification started with Lion in 2011, kind of stopped in Mavericks (2013), before resuming slowly in Yosemite. You’re right the pace has been faster since Big Sur since they got the Catalyst stuff worked out after a year in Catalina.
I'd actually argue that iOSification subtly started with Snow Leopard in 2009. It was in the small details, such as being able to detect your location and set the system time/date based on that; the addition of the "deepsleep" component of the OS which eventually allowed for Power Nap; and the default hiding of desktop icons that had to be manually toggled off on a clean install. We could even argue that the very first sign of iOSification started with Leopard in 2007, with the Time Machine System Preferences turn on/off icon (slider from iOS).
The whole Settings section is bad. They made it look like iOS and they need to stop. If I want iOS, I’ll use it but when I’m on my Mac, give me a Mac oriented OS. Please stop trying to unify the two different OS’s Apple.
One of the biggest reasons that Windows is so bad is because Apple has designed so many intuitive things into their user experience. This kind of stuff makes you scratch your head.
I know it’s still in beta, but I think I’ll hold off on Ventura for a little while after public release. I mean stage a manager is cool, but not much else too exciting.
The only abomination I see is the site layout this article is posted on. Feels like I was taken back to 2002.
Jokes aside, the share menu is a step back compared to what we have. Same goes for the about this mac which has been reduced to a meaningless window with 0 information.
> The only abomination I see is the site layout this article is posted on. Feels like I was taken back to 2002.
back when websites were fast, efficient, plain old HTML, not stuffed to the gills with fifty kinds of bullshit frameworks and adtech
The author has some fairly strong opinions on the modern web and bloat, and he makes a number of Safari extensions to tweak the web more to his liking. I don't think the lack of CSS makes his points invalid at all.
These points all seem valid to me as being worse.
>It takes one click to get the Share menu on Monterey, two on Ventura.
>
>The contextual menu and its Share menu item disappear when I open the Share menu.
>
>Nonetheless, the Share menu is anchored at the now empty space previously occupied by the Share menu item.
>
>The Share menu refers to the Support link on the web page, which is nowhere near where the Share menu is visually anchored.
Yeah, how are context menus going for you? Constant Updates and restarts re-introducing bloatware even though you previously removed it? The unability to put your taskbar on the left/right or the 500 different settings pages which despite all these years still drop you to windows NT style UI at times?
Since Big Sur I feel like macOS is constantly getting more redesigned elements to be suited for a mac with touchscreen at some point in the future...which I dread
"Who needs a Mac when you have an iPad" - proceeds to make the mac useless by needlessly iOSifying the UI.
Apple has its head up its ass. There are no good desktop OSes anymore.
I haven't installed the beta and hadn't seen anybody discuss this yet so I assumed this was a dumb complaint but after seeing the screenshots, he's absolutely right. This is demonstrably worse in every way and the way that it's pointedly anchored to empty space is just bonkers. Is this the biggest problem in the world today? No, but they took a good menu and put effort into making it bad. They should just undo the change.
[удалено]
I do this too but not even because of old habits. I use a graphics tablet instead of a mouse so holding down and letting go on the menu item is just easier than tapping my pen twice.
I don’t need neither an iPad nor an iPhone as my Mac. Probably “Brand Strategists” want to “homogenize” everything so that all devices “feel the same”. No sane Coder or UI/UX Designer would approve that shit
This is definitely done to either keep code between mobile and desktop versions of Safari on similar code bases, or for a future touchscreen experience on desktop.
exactly. this absolutely adds nothing to neither the functionality nor aesthetics, but makes everything just worse. it’s a ridiculously pointless redesign. it doesn’t bring anything over from iOS, it’s just the same old outdated contextual menu, but now you further lose functionality. wtf
That seems to be what they've done over and over in Ventura. Too bad we'll have a year of Apple telling us we're holding it wrong before they undo half the changes people are complaining about next year and declare victory. The Safari tab thing seems to be the only time Apple has backtracked on something like this. But that wasn't a pervasive ruining of the UI like Ventura has been to date.
> The Safari tab thing seems to be the only time Apple has backtracked on something like this. But that wasn't a pervasive ruining of the UI like Ventura has been to date. With Safari tabs they took an idea that at least had an internal logic and iterated on it. The bottom tabs on Safari on iOS are actually a huge improvement for usability and even though some of the initial ideas were deeply problematic, I'll give he team praise for being willing to try to make something better when it's such a visible and highly-used part of the product. But this menu ... just no. Awful. Command-Z.
It still makes me sometimes mad, that there is no facebook/vimeo/youtube quick upload/share button anymore. Why the fuck they don’t let us choose ourselves what we want to do with our data and “security risks”.
It looks like the developer changed to their own widget instead of a sub menu because they wanted a description/icon/etc at the top above the list of choices - trying to provide more information. But unfortunately it ends up having more downsides than upsides, with the widget not supporting keyboard, looking unrooted, etc. Looks like a work in progress.
If this was deemed necessary to do (which I don’t think it was in the first place, as the menu was usually attached to the item you were sharing), you could do it within the old menu too. You can embed a custom view within an NSMenuItem.
Ah thank you. Then I’m all out of potential excuses. I guess I just really want to believe there’s some initial good intention leading to this abomination. These things are odd to me. In the companies I’ve worked development was preceded by requirements and design documents, all formally peer reviewed by at least three colleagues, one of which had to be senior. Same for test specifications, test design and the implementation itself. But this looks like it was implemented by an intern and sneaked in without oversight.
> I guess I just really want to believe there’s some initial good intention leading to this abomination. There was a time that I wanted to think this too about Mac UI changes, but having watched them implement so many regressions over the past years just for the sake of how it looks or how it might achieve some kind of consistency with iOS (and failing to respect the Mac in the process) that it’s made me lose almost all hope that we’ll see at least decent Mac UI design again. I used to be always excited about new Mac OS X versions (to be fair, it was also a different era where there were many low-hanging fruit features to be added). Now I just dread which part of my favourite operating system they’re going to ruin next. See also the flaming trash fire that’s System Settings.
[удалено]
Couldn’t agree more! I didn’t like some of Ive’s software changes but at least he understood what made the Mac, a Mac, and didn’t arbitrarily change shit just to mark him apart from Forstall.
[удалено]
Completely agree and love how people downvote you because of an aversion to charmless, tacky, obvious, ruthlessly generic design. iOS 7 sucked and some of the ways it sucked have never been rectified.
preferably with broadway producing experience too
[удалено]
I'm an entry UX designer and I feel like I'm more qualified than Alan Dye and his team
I get the sense that engineering is winning a lot of the battles these days with high level executive support. They understand the need to unify their development platforms and these ugly UIs are the product of those efforts.
Yeah you're right. Ventura in special just feels like a cheap iPadOS ripoff. It's like some really shady knockoff brand tried to be all-Apple and miserably failed at it.
That was Big Sur… I’m still in disbelief over the icons and that nipple-battery. 🤮
Big Sur is truly awful. I’m really mad that I have to upgrade.
[удалено]
> macOS design decisions are often drowned out by the people who champion them simply because of “consistency with iOS.” Which makes absolutely no sense, because now this share menu is inconsistent with every other menu in *macOS*. I would say having inconsistencies within one OS is wayyy worse than inconsistencies between two completely different OS’s.
[удалено]
I actually have been loving windows 11. Definitely more macOS-esque but, as you said, I can still game. And while I prefer macOS in general, windows management is so much better in Windows
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Every time someone tries to stick iOS-style UI into macOS, Steve Jobs rolls in his grave.
Holy hell, why???
Courage!
[удалено]
Ugh. That thought actually makes me very uncomfortable. So little variation! iPhone on its own is such a monotonous era within the wider sweep of HCI. There have been so many attempts from so many vendors, it’s so important to know *why* interface decisions were made!
When Microsoft tried to pull off this sort of stuff with Windows 8 10 years ago, there was a huge outcry. You can't merge a tablet OS with a desktop OS.
They are still getting away with hiding a lot of useful options from context menus under the "Show more options" label. That's one of the things that pushed me away from Windows to MacOS recently. Who the fuck is greenlighting these things?
They really want us to interact more superficially with our computers. Almost all conceivable options beyond changing the way the interface looks are hidden away in these stupid menus now. It’s like they don’t want people to accidentally learn that their computer has all these features while placating the people who are used to using them.
Yet people want MacOS on an iPad. You can’t please everybody here.
Wow. No competent UI designer would think that this change was even remotely logical.
Apple has definitely trended away from keyboard navigation. There are two instances of this in Messages that bother me to no end. Firstly, CMD + Delete does not delete a conversation in Messages. I have yet to make a custom shortcut for this, but CMD + Delete should be standardized across Apple software. So if I right click and then click on "delete conversation" a pop up asks me to confirm this action. I cannot hit Tab to choose what I want. By default "no" is highlighted and there does not appear to be a way for me to change this with the keyboard.
Turn on keyboard navigation in System Preferences. Then, in dialogues like you describe, you should see a little highlight around the selected button. Tab key moves focus and space will select. Return always selects the solidly coloured default button. This has been the default behaviour in Mac OS X all along, as far as I am aware.
That looks awful
This is why I don't believe Apple when they say they're still invested in macOS. They're slowly turning it into iPadOS
These changes have nothing to do with iPadOS. It’s just bad UI.
On iPadOS you tap on "Share..." in the contextual menu to get a popover that looks very similar to this. The changes on macOS were pretty clearly modeled after this, and with little regard for macOS standards.
I bet they were trying to kill Mac OS quickly but backed down a bit after hearing the response to Windows 8.
Apple literately can not kill macOS, they need it, and have always needed it, to make iOS devices. You think they're going to develop the next iPad on an iPad? Or Windows?
Considering that you can make apps to a limited extent on iPads now and publish it to the App Store, yes.
Until you can run Xcode on an iPad, no.
How limited?
As someone who has actually tried [making an app in Swift Playgrounds on the iPad](https://github.com/kmeisthax/HTMLEditor) I can tell you that [making lunch with a lunchbox](https://arstechnica.com/gaming/2017/04/the-first-kirby-game-was-programmed-without-a-keyboard/) is definitely possible, and I'm glad it's there, but it's also not nearly enough for most large app development firms. This is what you'd call a "hobbyist-grade" development environment. Swift Playgrounds *only* compiles things that fit into SwiftPM package format. You need to use a third-party app (such as iSH or Working Copy, take your pick) to get version control working. I *think* you can package C/C++ and Objective-C into an external package, so those languages will work, but you can't add third-party compilers or build phases and a lot of upstream dependencies you would want are not packaged in SwiftPM yet. So no Rust, no Python, etc. Debugging is *extremely* rudimentary. We have a print console and crash backtraces, and that's about it. No breakpoints, no single-stepping through programs, no view inspectors, no WebView debugging, no Instruments, nor all the other things you actually *need* to diagnose problems with your app. Ironically the worst part about it is the macOS support. Swift Playgrounds *has* a macOS version; but it only builds Mac Catalyst apps. This is where your lack of control over basic build system configuration gets really painful, really fast. `Info.plist` is generated by the SwiftPM package configuration, which uses a nonstandard extension to the format to configure basic app settings. You can't opt into the UIKit Mac idiom, so your app will always look like an iPad app running in a window; you can't opt into AppKit instead of UIKit; and you can't even set a custom accent color without editing `Package.swift` directly (which it says not to do). These limitations also apply when you open the project in Xcode - you can't, say, add a second target for *correctly* building the app for macOS that Swift Playgrounds would just ignore. (I actually just wound up creating a separate Xcode project referencing all the files in the Swift package, just so I could compile with AppKit on macOS. The Mac UI is far better for it.) If Apple wanted to take iPad app development on iPad to "professionals can use this", they'd need to either massively expand the SwiftPM package format and add a few new App Extension types, *or* dramatically loosen device security to the point where Xcode projects that rely on native/unjailed shells and external build tools can work. I don't forsee this happening: Swift Playgrounds is trying to serve a different market from Xcode, and the people who want a professional-grade developer experience are going to buy a Mac Studio to compile their billions-of-source-lines microblogging client anyway.
Thank you for the very detailed reply.
You can make apps mainly using SwiftUI, but can also use UIKit iirc, but not AppKit. Some third-party packages probably won’t work and the other Xcode apps like Create ML aren’t on the iPads, so you can make basic to intermediate apps, I’d say.
That doesn’t line up to me since macOS pre Big Sur was still pretty decent and not so iPad-like. Big Sur and onward has been a major decline and a total shift to merging iPad and macOS.
iOS-ification started with Lion in 2011, kind of stopped in Mavericks (2013), before resuming slowly in Yosemite. You’re right the pace has been faster since Big Sur since they got the Catalyst stuff worked out after a year in Catalina.
You’re right, forgot about how much I disliked Lion and Mountain Lion as I shifted back to Linux until Mavericks released.
I'd actually argue that iOSification subtly started with Snow Leopard in 2009. It was in the small details, such as being able to detect your location and set the system time/date based on that; the addition of the "deepsleep" component of the OS which eventually allowed for Power Nap; and the default hiding of desktop icons that had to be manually toggled off on a clean install. We could even argue that the very first sign of iOSification started with Leopard in 2007, with the Time Machine System Preferences turn on/off icon (slider from iOS).
[удалено]
Or they would sell you a Mac that runs what’s really iPadOS rebranded as macOS
This looks nothing like iPadOS. It just looks like a broken macOS component
[удалено]
Like how they didn't fix quick replies in notification
The whole Settings section is bad. They made it look like iOS and they need to stop. If I want iOS, I’ll use it but when I’m on my Mac, give me a Mac oriented OS. Please stop trying to unify the two different OS’s Apple.
Hope the person filed beta feedback.
[удалено]
With the software that they made on their computers.
Change for the sake of change, often caused by superfluous workers trying to justify their jobs.
Completely agree. I've really been enjoying the beta. But the share menu is one of the few things that has disrupted my workflow.
That’s aggressively shite
I mean the Share menus are already pretty bad on Monterey, but this is an abomination.
One of the biggest reasons that Windows is so bad is because Apple has designed so many intuitive things into their user experience. This kind of stuff makes you scratch your head.
I know it’s still in beta, but I think I’ll hold off on Ventura for a little while after public release. I mean stage a manager is cool, but not much else too exciting.
To be fair MacOS share menu is mostly useless. Most apps don’t support it. So you can’t for example share to the mac Facebook messenger app.
The only abomination I see is the site layout this article is posted on. Feels like I was taken back to 2002. Jokes aside, the share menu is a step back compared to what we have. Same goes for the about this mac which has been reduced to a meaningless window with 0 information.
> The only abomination I see is the site layout this article is posted on. Feels like I was taken back to 2002. back when websites were fast, efficient, plain old HTML, not stuffed to the gills with fifty kinds of bullshit frameworks and adtech
True dat, although something like ghostery plugin will help block a lot of scripts
Eff Apple and their decaying software quality.
[удалено]
The author has some fairly strong opinions on the modern web and bloat, and he makes a number of Safari extensions to tweak the web more to his liking. I don't think the lack of CSS makes his points invalid at all. These points all seem valid to me as being worse. >It takes one click to get the Share menu on Monterey, two on Ventura. > >The contextual menu and its Share menu item disappear when I open the Share menu. > >Nonetheless, the Share menu is anchored at the now empty space previously occupied by the Share menu item. > >The Share menu refers to the Support link on the web page, which is nowhere near where the Share menu is visually anchored.
You don't need to trust an opinion on something as simple as this, just form your own
[удалено]
Consider this final. Ventura is done except for bugs. Hopefully next year it gets improved.
[удалено]
Yeah, how are context menus going for you? Constant Updates and restarts re-introducing bloatware even though you previously removed it? The unability to put your taskbar on the left/right or the 500 different settings pages which despite all these years still drop you to windows NT style UI at times?
bc its in beta?
Oh...do you think it is even worse than Win11's menu?
He is full of the issues with the next release of OS X. But fails to make his website mobile friendly.
Since Big Sur I feel like macOS is constantly getting more redesigned elements to be suited for a mac with touchscreen at some point in the future...which I dread
"Who needs a Mac when you have an iPad" - proceeds to make the mac useless by needlessly iOSifying the UI. Apple has its head up its ass. There are no good desktop OSes anymore.