Live data from Hacker News

macOS 13 Ventura review

arstechnica.com

121–130 of 185 posts

Re: macOS 13 Ventura review

#121

Earlier quoted context omitted.

Keyboard and trackpad/mouse is a huge difference from only a touchscreen.

Don't iPads have that as well via the official case?

You are correct, they do, via the official keyboard/trackpad case. Or you can even just connect any other bluetooth keyboard+trackpad (including the dedicated magic keyboard+trackpad for macs). And most of the keyboard+trackpad shortcuts/gestures are already the same on both macOS and iPadOS

Re: macOS 13 Ventura review

#122

Still waiting for Display Port MST support over USB-C to enable monitor daisy chaining.

You are never going to get it for the current machines is my guess. Technically it should work with 2HD screens rather than 1 UHD screen, but I don't know.

Re: macOS 13 Ventura review

#123
post #86

Does anyone else dislike the "phonification" of desktop UIs? Desktop and phone use are very different, with very different screen real estate.

Everyone dislikes it. This is among the reasons why Windows 8 was such a massive failure, it tried to force a UI that kind of makes sense on a small touch screen on PCs where it didn't make any sense.

Worse, Windows 8 failed after the failure of the Windows phone, which it copied.

Re: macOS 13 Ventura review

#124
post #40
post #37

Earlier quoted context omitted.

> so it has to go in the dumpster with a great battery, a fine screen and a processor that could easily be used as a server, video player, browser etc. Why would it have to go in the dumpster if it still works well? This reasoning is why we have exessive e-waste, not the lack of upgrades...

Because you won't get security updates after 2 years or so.

Apple released a security update for iOS 12 a couple of months ago for devices going back to 2013’s iPhone 5s [1].

[1]: https://support.apple.com/en-us/HT213428

Re: macOS 13 Ventura review

#125

Earlier quoted context omitted.

Yeah, I am a little disappointed that this is the first upgrade that I cannot get with my late 2015 iMac. I'd use the legacy patcher perhaps, but I don't see much on this new version that I would want, so i'd rather keep things offical for now, to avoid any issues. Yes, I get that this machine is 7 years old, but I cannot tell from using it, everything is extremely fast, I upspecced it when I bought it and maxed out…

I had every desire and intention of upgrading my desktop (late 2015 iMac) to the newer hardware, right up until they decided this hardware is somehow incompatible with the newest MacOS. They've basically just ended 20 years of Mac for me. Pity.

[deleted]

Re: macOS 13 Ventura review

#126
post #98

This upgrade is going to cost me a lot of money. They've dropped support for my beefy 2016 MBP. Soon enough the latest version of XCode is going to require Ventura and I won't be able to build my app. Meanwhile, Linus is only just starting the discussion to drop the 486 from the Linux kernel.

This has more to do with the 486 (or clones of it) having adoption in embedded platforms that run Linux than Linux being reluctant to let support for old consumer-oriented hardware die. For example, Linux doesn't even bother with attempting to mitigate speculative execution vulnerabilities on Intel processors running in 32-bit mode, you are just told you are vulnerable and that's that.

What's the chicken and what's the egg? A large part of the reason that Linux is popular in embedded is because it has a long support period.

Re: macOS 13 Ventura review

#127

Earlier quoted context omitted.

System Settings only uses half of my 13" MacBook's screen width. That seems entirely reasonable. There's no shortage of pixels here... And why would you have to mentally put the sidebar together with the left side of the screen? Do you complain about tabbed dialogs not having the tabs align with the top of your physical screen? When you have more "tabs" than can fit horizontally (e.g. more than 5-7), the best solutio…

Right on - so I'd much prefer the focused user pane of leaving the previous "table of contents" view. This is what happens in Privacy & Security System Settings now, click any of them and leave to a focused pane about the topic you just asked about. If you're wrong, go to the back button. Focused Panes of action to me in a desktop environment is correct for the context. Trackpad and MagicMouse environments to me are…

The goal of good UX isn't to "fit n-times the number of settings". It's not about maximizing density (or not wasting pixels or real estate).

It's about clarity, affordance, organization, and not getting lost. And also, yes, consistency as you say -- this has become more consistent with iOS settings, which is a good thing.

(I also don't know what "click/twitch" means. Googling it gives me zero results that aren't for Twitch streaming. But in any case, the navigate/back paradigm has nothing whatsoever to do with which input device you use. Neither mice, trackpads, nor touchscreens have any kind of consistent "back button". Sometimes there's some side button or side swipe that works with some programs, sometimes there isn't.)

Re: macOS 13 Ventura review

#128
post #120

Earlier quoted context omitted.

Put ChromeOS Flex on it. It’s a flavor of ChromeOS/Neverware meant for old PCs and Macs that can’t keep up with Windows and macOS. https://chromeenterprise.google/os/chromeosflex/

I want a Mac. I don't want a Mac and a Chromebook. But maybe someone else would use my old Mac as a Chromebook. Except there are zillions of cheap Chromebooks around already.

In that case, you have either the opencore/hackintosh route or you can simply run on the last compatible OS.

There is a market for nicer-feeling Chromebooks, so ChromeOS Flex is a partial remedy for e-waste.

Re: macOS 13 Ventura review

#129

Earlier quoted context omitted.

Right on - so I'd much prefer the focused user pane of leaving the previous "table of contents" view. This is what happens in Privacy & Security System Settings now, click any of them and leave to a focused pane about the topic you just asked about. If you're wrong, go to the back button. Focused Panes of action to me in a desktop environment is correct for the context. Trackpad and MagicMouse environments to me are…

The goal of good UX isn't to "fit n-times the number of settings". It's not about maximizing density (or not wasting pixels or real estate). It's about clarity, affordance, organization, and not getting lost. And also, yes, consistency as you say -- this has become more consistent with iOS settings, which is a good thing. (I also don't know what "click/twitch" means. Googling it gives me zero results that aren't for…

Yeah, I'm not classically trained to speak in the right terms. The whole idea for me is, can I get what I want to do, done, in a more enjoyable way? That to me is all things - the ideas I threw out were just brainstorm novice ideas that I would find helpful. Enjoyable also becomes philosophical - which is good - but should be understood through the way it works, obviously + consistently.

Yeah, click/twitch is a made up term just now. Though I would say an affordance of the input device one uses does dictate what is 'easiest‘ or 'most natural' to use - a quick swipe once the edge of a window is reached, to signal either refresh (for pull down) or go back / forward for horizontal edges sure feels nice on a trackpad. I believe had Apple had a slide swipe via edge earlier in its life - we would have gone straight to glass only devices, no home button.

Re: macOS 13 Ventura review

#130
post #98

Earlier quoted context omitted.

This has more to do with the 486 (or clones of it) having adoption in embedded platforms that run Linux than Linux being reluctant to let support for old consumer-oriented hardware die. For example, Linux doesn't even bother with attempting to mitigate speculative execution vulnerabilities on Intel processors running in 32-bit mode, you are just told you are vulnerable and that's that.

What's the chicken and what's the egg? A large part of the reason that Linux is popular in embedded is because it has a long support period.

My point was that the support for 486 was being kept due to its embedded applications and not so someone with a 486-based desktop PC can expect to build a modern distribution on it and achieve full functionality equivalent to a modern machine.
Post reply on HN