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

Ventura Issues

mjtsai.com

Post reply on HN
Print view View original

121–130 of 135 posts

Re: Ventura Issues

#121

Post by mattgreenrocks »

gfxgirl wrote: post #41
mattgreenrocks wrote: post #31

Just today I tried to look for how to switch to using the discrete GPU on my 2019 Intel MBP, but I couldn’t find a setting for it. Is it gone?

was there ever a setting for this? I always used gSwitch or gfxCardStatus to varying degrees of success

It was labeled "Automatic graphics switching" in past releases. It appears to be gone completely. I just confirmed it was under Battery on 12.5.1. This is a shame. The Intel GPU on the 2019 MBP is pretty anemic and it is definitely felt when programming in some editors.

Re: Ventura Issues

#122

Post by cassianoleal »

xsc wrote: post #118

Not specifically Ventura, but anyone having issues having os remember monitor position? My Mac mini running Monterey can’t flips the monitor on login/unlock more often than not.

I had never had issues with external monitors until Ventura on the M1 Air.

Now, each time I plug it in to the monitor whatever will happen is pretty random. Sometimes it gets the full EDID from the monitor and everything is as I want it to be, including resolutions, refresh rate and positions. Sometimes, I get partial EDID and only some refresh rates available (my monitor goes up to 144Hz, sometimes macOS can only do 60 or 75Hz). When that happens, resolutions and screen positions may or may not be ok. Most of the time the laptop screen is set to mirror the monitor which is pretty much never what I wanted.

Other times it just doesn't properly detect the monitor which stays blank until I disconnect and reconnect - at which point any of the above paragraph might happen.

More rarely, the computer freezes and I need to force shutdown.

Re: Ventura Issues

#123

Post by jkmcf »

Sharing in case this helps anyone.

Since upgrading to 13.1, notifications have been severely problematic. Slow, delayed, clicking on Slack notifications would open the app minutes after the click.

This stackexchange reply solved the problem for me: https://apple.stackexchange.com/a/219528/34701

  cd `getconf DARWIN_USER_DIR`
  rm -rf com.apple.notificationcenter
  killall usernoted; killall NotificationCenter
  # restart computer

Re: Ventura Issues

#124

Post by awesomegoat_com »

userbinator wrote: post #51

Those on the Windows side are just as if not more angered by Windows 11 too. The software industry has become an example of quantity over quality, features over fixes, change and novelty over stability, diversity over excellence. Instead of gradually approaching perfection as bugs are fixed over time, software gets needlessly rewritten and introduces a bunch of new bugs. Thanks to the wholly misguided focus on "devel…

> The software industry has become an example of quantity over quality, features over fixes, change and novelty over stability, diversity over excellence.

Well, it is all caused by senior managers counting JIRA tickets and certified scrum masters pushing the sand through the python.

Software enthusiasts in sandals loving technology have been replaced by people driven by compensation structures.

Re: Ventura Issues

#125

Post by KerrAvon »

dagmx wrote: post #94
supercucumber wrote: post #82

Earlier quoted context omitted.

System Preferences was rewritten for Ventura in SwiftUI, which is absolutely not ready for production, especially on Mac. Speaking from personal experience, I recently wrote a simple macOS app using SwiftUI. I found the framework to be slow (why does it use so much cpu/memory when idle??), unintuitive, and awkward to use. Despite being in its 4th year, SwiftUI is still very much beta software, and I wouldn’t recommen…

As a counterpoint, I’ve done several Mac apps with SwiftUI for internal use and it’s been quite pleasant. Early SwiftUI was definitely rough, but it’s quite nice now as of Monterey and Ventura. If you’re seeing high CPU use and slow performance, it might be due to high usage of ObservableObject or other things that may be triggering updates under the hood more often than need be. SwiftUI is very sensitive to the data…

Apple really needs to put some effort into evangelizing SwiftUI — some of the problem is poor or nonexistent Apple documentation and some is that every Stackoverflow answer is obsolete because the documentation is still so poor.

You can still run into walls with SwiftUI, but there are fewer of them than there used to be.

Re: Ventura Issues

#126

Post by KerrAvon »

andrekandre wrote: post #74
baggy_trough wrote: post #55

Earlier quoted context omitted.

Agreed, the Settings app is horribly ugly now. So is About This Mac.

its not only ugly, its harder to use, more confusing where things are placed now...

Am I the only person who could never find where anything in the old prefs app was? I started using OS X in 2001. The old prefs app also didn’t scale.

Re: Ventura Issues

#127

Post by awesomegoat_com »

skissane wrote: post #30
mberning wrote: post #5

Apple is badly, badly in need of a “code red” style freeze on new features for macOS and iOS. Even very basic things which should be rock solid are not. I just had a kernel panic when copying files to an smb mount. No issue when I do the same copy mounted as nfs. Ridiculous in this era.

I don’t understand why Apple doesn’t invest more in testing and bug-fixing. It is not as if they can’t afford it. Bugs lead to unhappy users, which in turn leads to brand damage. You’d think it would make business sense to spend more on improving quality and hence preventing further such damage, possibly even reversing some of the damage already done-convince people “Apple is different now”, some people will forget t…

Successful companies do not operate on common sense kind of framework. That's an art available only to peons.

Re: Ventura Issues

#128

Post by awesomegoat_com »

userbinator wrote: post #58
mberning wrote: post #5

Apple is badly, badly in need of a “code red” style freeze on new features for macOS and iOS. Even very basic things which should be rock solid are not. I just had a kernel panic when copying files to an smb mount. No issue when I do the same copy mounted as nfs. Ridiculous in this era.

I just had a kernel panic when copying files to an smb mount. Apple rewrote the SMB code to make it closed-source starting with 10.12, I believe; the immediately noticeable effect was that it became far buggier.

Hahaha, spend more money and end up with inferior result.

Must have had some serious managers involved.

Re: Ventura Issues

#129

Post by Gigachad »

Nextgrid wrote: post #119
Gigachad wrote: post #90

Earlier quoted context omitted.

I was on the eagerly checking when this update came out. Wanted that iphone as webcam feature. It's such a huge improvement. My webcam no longer looks like a washed out newspaper printout. Freeform is also a nice new tool I'm looking forward to using as well as Advanced Data Protection for icloud to have end to end encrypted cloud storage at last.

On the other hand, Ventura prompts me (with a huge window full of whitespace) about using my iPhone as webcam every time an application opens the (built-in) webcam, with the two options being “Get started” or “Remind me later”. They seem to have forgotten the “fuck off” option, as usual for modern tech. What is the user supposed to do in cases where they don’t want/need to use their iPhone as webcam?

Hmm, not ideal but I’m pretty sure if you just go through that prompt it sorts it out. The iPhone becomes another listing in the webcam list but you can pick the built in one and it won’t prompt you to switch.

Re: Ventura Issues

#130

Post by waynecochran »

j_crick wrote: post #114
waynecochran wrote: post #80

Earlier quoted context omitted.

Yep. I just updated my desktop from 10.14 to 10.15 only because I had to. Best to stay a couple of years behind. Not like the Apple of 15 years ago where their stuff just worked.

I’m still on Mojave because I hate new UI changes and such. Don’t know for how long it’s last but for now it works. One annoying thing is that an iPhone SE 2020 that I bought now requires a fresher version of iTunes that is not available for 10.14. I guess I’ll just wait until it annoys me too much and eventually switch to some android.

I would have stayed on Mojave, but what finally pushed me is that I didn't have full C++17 support for Xcode and the underlying compiler and libraries for some reason I still don't understand. e.g., I couldn't used std::filesystem stuff.
Post reply on HN