5 ms·
As an mac/iOS user, I find it embarrassing that Apple's entire new flagship CPU line cannot run its newest OS. It's a bad look.
by nickthegreek 3y ago
As an mac/iOS user, I find it embarrassing that Apple's entire new flagship CPU line cannot run its newest OS. It's a bad look.
- whalesalad 3y agoIt can run the latest OS, it’s just that the update flow isn’t working. If you download the installer from the store and run it, it works.
- FireBeyond 3y agoApple is all about it "just works". Flagship product, flagship OS, "the flow isn't working". Hm.
- whalesalad 3y agowell tbh the system does work. it will boot and be just fine and i'm sure 99% of users won't even realize they're a version behind. these days the differences are pretty minor so there are not a lot of capabilities a person would miss out on.
- FireBeyond 3y ago> i'm sure 99% of users won't even realize they're a version behind The people clamoring for launch day or early access to the latest model "won't even realize"? I'm going to agree to disagree on that one. They'll realize at first boot and the very different login screen (especially if they're upgrading from a previous Mac).
- whalesalad 3y agoThe last 3-4 versions of MacOS have been virtually identical on the surface. I don’t think you’re correct.
- Clamchop 3y agoI don't really get this perspective. Making it appear that things "just work" is not even showing users the option to try an unvalidated or nonfunctional combination of hardware and software. Staggered releases across models or user fractions are often planned as a matter of routine, even. Apple certainly doesn't always get it right, but this ain't an example of it. They just bricked some MacBooks during Sonoma updates! Now that's shitting the bed.
- FireBeyond 3y agoThey weren't forced to push the M3 out so (relatively) quickly after M2 systems. Their schedule was of their own making, and yet you end up with "our newest users need to use older software, because we couldn't wait for testing to release our new hardware". That's why.
- altairprime 3y agoUnless you worked at Apple in a team involved in this, there is no reason for you to need to feel embarrassed or ashamed here. Binding your self-image to the actions of an organization puts you at risk of harmful outcomes when – not if – their position eventually conflicts with your own. If their actions are so egregious that you decide to end your support of them, then that’s perfectly understandable. However, judging you to be at fault for their actions would be nonsensical, and has no place here.
- supertofu 3y agoI believe OP was an employing a rhetorical device called hyperbole to emphasize their disapproval of the situation.
- altairprime 3y agoI’m not so sure. HN is vulnerable to “don’t talk about my favorite sports team that way” problems, wherein sometimes we get our selves confused with our favorite team and get defensive when discussion about an organization is misread as attacks on our selves (for a variety of examples, review some of our cryptocoin or non-OSI code licensing discussions). If they’re seriously expressing their beliefs, then taking that seriously is a courtesy they deserve. So I chose the best faith interpretation, to respect their beliefs as stated rather than risk insulting their intentions or beliefs by declaring it as hyperbole, and offered a tidbit of hard-earned wisdom from this old graybeard flamewars refugee. If it’s not applicable, that's fine, no harm done.
- nickthegreek 3y agoIt was hyperbole. I should have been clearer and stated that They should be embarrassed.