ARM isn’t the problem. Some games have native ARM ports, and x86 games can be run by Rosetta. It’s not as fast as native, but broadly comparable with the performance of the previous gen Intel chips they replaced.

A bigger problem on macOS is that they dropped support for 32-bit software a few years ago in Catalina. Not a problem with newer games, but it decimated Mac users’ Steam libraries.

And the biggest problem is that Apple just doesn’t give a shit about gaming. Every few years, they claim they’re going to do games, but quickly forget about it. They’ve never put decent video cards in Macs, and never hesitate to throttle hardware if proper cooling would mean a larger enclosure, so AAA games typically arrive on macOS years late, when second-rate or integrated video cards can run them.

If they actually cared, they’d have their own Vulcan implementation. Instead, they’re focused on their own proprietary Metal API.

Basically, Apple and AAA game studios have been ignoring each other for decades.

Jau. eAuto hilft nicht viel, weil das heutige Auto an sich nur bescheuert ist.

Um die 100KG Mensch etwa 100KM am Tag will man befördern. Und dazu müssen 1,5 Tonnen Stahl 22 Std. am Tag komplett nutzlos im Weg rumstehen? Völlig hirnrissig.

I haven’t touched the thing in three years.

I just remember that it had pace where it should have average speed. That is all.

Now go away. I’m not interested in defending myself to someone like you, who’s been nothing but nasty.

A 2022 Toyota Corolla gets around 40mpg highway and squeezes 5 people inside so it uses 0.5 gallons per person per 100mi.

5 people in the Corolla is 2–3 times as many people as are at all likely to be in there. That’s a very skewed number.

When using realistic numbers, cars come in at about the same per mile as large commercial airliners. (Flights tend to be far, far longer of course.)

A fella figured out how to cash in on VC-subsidised deliveries by ordering from his own restaurant.

That’s not the Vivoactive cycling app.

Nah you’re right and this person has obviously never used a Garmin.

You mean that you didn’t bother to read my comment properly before personally attacking me. Let me guess, you’re from Reddit.

I only cycle, so I couldn’t comment on the other apps.

They were Vivoactives. They had pace, not average speed.

Regardless of what the focus of the watch is, the cycling app should show cycling stats.

It’s incredibly low effort to get something so basic wrong.

I said average speed. Learn to read.

Apple Watch.

I had a couple of Garmins before and the difference is night and day. The Apple Watch isn’t perfect, but it’s clear that a lot of thought went into it.

The Garmins on the other hand, were lowest of low effort.

They blatantly didn’t talk to even a single cyclists while building their cycling app.

Cyclists use average speed, not pace. Even the junkiest $3 cycle computer from Ali Baba gets this right, but not Garmin. They just copy-pasted the running screen.