> At the cost of a generally worse end user experience and no offline ability.
Yes. This is a cost and a benefit you weigh according to the capabilities of your development team. If there is nobody to outcompete you, that is factor into the decision.
> I am glad Apple didn't do that and stayed native for nearly everything. This is a big selling point for me.
Right, but Apple also perfectly exemplifies the problem with that approach - their software is incredibly limited, and can only run on a ridiculously small number of computers. Even if the software is good, which ehhh, but even if it is - there are cons to that approach.
To expand, this also hurts the customer in a lot of direct and non-direct ways. You're forced to buy Apple hardware, and that hardware might not meet your capabilities. This further fuels anti-consumerist anti-repair behavior, because they know that their computers are the only ones you can use.
And, since they create their own market, they kind of have you in golden handcuffs. If their prices go up, which they do and already are high, you're along for the ride.
I didn't overstate them, if anything I was far too generous.
It's plainly true that Apple software locks you into Apple devices, which are more expensive than they should be. In addition, those devices are some of the most anti-consumer computers made. You can't repair them, they're locked down.
What Apple does is impressive, sure. But let's not pretend that making mediocre software that runs on 1% of computers is anything compared to the Web. They have fundamentally different goals, which is why native Apple software doesn't compete with the web.
It doesn't. I work across both Windows and Apple stuff and have zero issues moving things back and forth on a regular basis. Hell even their email is plain IMAP+SMTP. Try that with O365/Microsoft.
As for the repair? You can literally buy parts here and repair them yourselves. I have actually had to replace a USB-C port on my last M1 MBP and it was dead easy. https://selfservicerepair.com/ . I see this everywhere I go: parroting the same misinformed garbage about their repair situation.
You just dislike Apple and can't wait to tell everyone about it.
1. I don't dislike Apple, I have multiple Apple products.
2. Apple devices are uniquely difficult to repair and this is done on purpose. For a long time, you couldn't do it at all. Now, you can... if you use Apple approved tools and parts.
It's just plainly dishonest to say Apple does not engage in some of the most rampant anti-repair anti-consumerist behavior in the industry. They do, and they have been for a long time.
Also yeah, O365 sucks. You know what else sucks? Webkit on IOS, iMessage, SwiftUI, Mantle. Apple loves loves loves their software vendor lock-in on technologies that nobody actually cares about. Just use real standards for fuck's sake.
Yes. This is a cost and a benefit you weigh according to the capabilities of your development team. If there is nobody to outcompete you, that is factor into the decision.