roopepal

> It seems that M4 chips can’t virtualise any version of macOS before 13.4 Ventura

13.4 was released on May 18, 2023. That's actually not very far into the past.

Anyway, what would be the most common use cases for this? And how common are those?

> Your website has a serious issue.

I was thinking the same. My (admittedly old-ish) 2070 Super runs at 25-30% just looking at the landing page. Seems a bit crazy for a basic web page. I'm guessing it's the background animation.

I find it amusing how you answer your own "question" before asking it. Why would they target the marketing material at people who already know they aren't going to need to upgrade?

I believe the previous design was around for well over a decade, so it did have a pretty good run.

> I'm surprised The Verge apparently doesn't know

Really? Personally, at this point, I'm generally more surprised when they do.

SwiftUI does not replace storyboards. It replaces UIKit(/AppKit).

You can build UIs without storyboards/Interface Builder in UIKit just fine. And writing your UI in code indeed easily solves the whole versioning conflicts issue that storyboards have.

So no, not a big argument for SwiftUI, but instead for writing UIs in code.

SwiftUI vs. UIKit and IB vs. code are two entirely separate discussions.

But yes, I totally agree, if you must use storyboards, keep them as small as possible.

According to the first 10 sources I see for a "define passenger" Google search, the pilot is not a passenger. One of those sources is even for legal purposes. I have also never heard anyone refer to the driver/pilot/crew as passengers. What am I missing here, is this some lingo specific to this context, or?

Yes, I do in general agree with that. I suppose my confusion really only applies in this particular context of , e.g., HN; I would expect software engineers to look at these issues differently than your average home or office user. It seems to me that this "easy to use out of the box" marketing is aimed at a different sector of users, and I would expect software engineers be able to look through this. Perhaps my expectations and assumptions are wrong.

I am just curious where all the willingness to tinker and solve problems appears to disappear when we move to macOS.

Windows spying on you? Oh, let's install this tool X and change a whole bunch of registry settings to prevent that.

App windows behaving annoyingly on Linux? Oh, let's just switch to a completely different desktop environment/window manager or what have you.

Too many icons in the menu bar on macOS? Yeah, I'm returning this machine. :)

> I hate how the window management works. I hate how annoying it is to get two windows to show side by side.

Plenty of window management apps and tools available. Rectangle, for example.

> I hate how there end up so many icons in the menu bar which are entirely unhelpful.

The only ones I cannot seem to be able to remove trivially are the clock and the Control Center. Solved in mere seconds by typing "menu bar" into the System Settings search. You could literally even just hold cmd and drag almost any icon out of the bar. Not to mention any of the more involved menu bar customization apps and tools.

Why does it seem like such "macOS bad Linux good" comments always compare the default macOS experience to a personalized Linux environment?

Why does an out-of-the-box Mac have to fulfill the same requirements we spent hours configuring for on a Linux machine?

Where does the capability or mindset to install a tool disappear when we move from Linux to macOS?

Just in case you did not notice, this did not actually happen, it was a hypothetical.