Hm… I’m all for open standards, but Apple should retain the right to develop features that work exclusively on their devices (provided their devices support alternative protocols to avoid total lock-in). As open-source and linux loving as I am, I’m a willing prisoner of the Apple closed garden because I appreciate how refined and integrated everything is. (Others’ experience may differ)
The experience can still be refined and integrated, without having closed systems for something as simple as sharing a file to another phone. Why would you be against adding more value to your device?
Maintaining backwards compatibility isn’t easy, and cross compatibility just adds more complexity.
The good and the bad of Apple not having the best backwards compatibility is they don’t have to waste time on that. They can do what they do well and make the experience as smooth and seamless as possible. And most importantly move quickly.
I mean just look at windows. Windows 11 has gotten so much shit because they’re trying to change so many things, but they legitimately just can’t. Or on Linux look at its backwards compatibility. That shits a nightmare. Things like flat pack should fix it. But it only fixes it if everything is on flat pack.
iPhone does notsupport file sharing over Bluetooth, so it invalidates the condition you put between ().
The way I read it, they’re not asked to follow an open standard, but to provide a specification for their own standard. That means that they could dictate the pace of development and others could decide for themselves wether or not to implement it for their devices. It’s similar to WhatsApp being forced to provide third parties with API access.
Also, they currently don’t support alternative protocols with cross-platform support and they’re not going to, unless forced.
