M3 Ultra being fastest in single core than M4 or A19 Pro doesn't make any sense.
Those chart also suggest that M3->M4 was a _regression_ in performance, which, is... an interesting conclusion.
3,943 karma · joined August 15, 2011
M3 Ultra being fastest in single core than M4 or A19 Pro doesn't make any sense.
Those chart also suggest that M3->M4 was a _regression_ in performance, which, is... an interesting conclusion.
Because you need TZ awareness to implement that in a way that most humans expect.
So you have to do the conversion at some point _anyway_.
If your app presents me data making the assumption that _my_ day is always 86400s, it will be _wrong_.
Making an assumption that a day 86400 seconds breaks at least twice a year in many parts of the world, and that's before we introduce leap seconds or possibility of your code running on hardware that itself travels across timezones.
I think this is a new design, with Apple having three tiers of cores now, similar to what Qualcomm has been doing for a while.
I think how it breaks down is:
- "Super" are the old "P" cores, and the top tier cores now
- "Performance" cores are a new tier and seen for the first time here, slotting between "old" P and E in performance
- "Efficiency" / "E" are still going to be around; but maybe not in desktop/Pro/Max anymore.
But the consensus seems to be that in English that would indeed count as four words ;P
Meanwhile, my carrier in Japan not only migrates eSIMs between phones with no issues; it even offered to migrate my wife's physical SIM to an eSIM when setting up a new phone; and it worked flawlessly.
The way my original eSIM here was provisioned was also surprising to me, in a "I didn't even know this is possible" way.
When signing up for a contract, I just put in my eSIM EID, and then a couple of hours later an eSIM was _pushed to my phone by the carrier_; without me having to do anything (other than confirming that I do want to install it). Lots of customer-facing telecom infra here is pretty bad; but the eSIM experience was as good as it gets.
Both iOS and Android have APIs for this, you (as the app developer) just mark the relevant fields in the app as login/password/etc, and the OS will interact with your chosen password manager to autofill and/or save them.
If you use the _digital_ MyNa card (e.g. the one in the Wallet.app; not the plastic one); the iOS SDK lets you only request the "is user more than XX years old" flag; without getting the actual identity: https://developer.apple.com/documentation/passkit/requesting...
Now, AFAICT nobody actually does this, but the technical ability is there.
I'm sure there's plenty of content (especially streaming content in mediocre bitrate) where people would be hard-pressed to tell the difference.
But I think if people went back to 1080p _panels_; they'd actually rather quickly notice how much worse the text-rendering is, and that the UI looks off for them.
Moving up to 8k would definitely be a smaller step-change in clarity than 1080p->4K and many people wouldn't feel it's worth spending extra; but I don't think it would be literally indistinguishable.
That strikes me as extremely counterproductive given the actually sensitive part of a BP is an (outside of the US) unsigned, semi-publicly-documented barcode.
I think the short, single clause, internal-monologue-ish sentences is what did it?
> I am reading the post again. It does appear the author is not fully aware what DFU is supposed to do.
That especially came off like an LLM being called out on being wrong about something?
The M5 Pro/Max variants aren't; but an M5 Mac is a thing you could have bought for a good while now.
But I do think that the writing was fairly central to the intended experience and design of the game.
Those are made in tiny teams. You can either spend more time tinkering with the gameplay mechanics and experimenting with the game parts; or you can put on your software engineer hat and make the code better (or, spend even more time to learn how to make the code better in the first place!).
This gets less true with scale of a team, and with 5000 people behemoths you probably should care _a lot_ more about the code; but ROI on improving the code in (relatively! Calling Blue Prince “small” is ridiculous.) small games is very dubious.