Uhm, I had pixel phone is the first Pixel. Once it started using wireless charging, I only use usb-c in three scenarios: I'm traveling and using a powerbank, I'm in a car and want to use Android Auto (for some reason my car has wireless Car Play, but not AA), or I'm on a couch and my phone is low on battery (never happened when I iPhone tho). For this reason, I travel with cables that have adapters for lightning. Annoying, but not the end of the world.

I realistically don't care what port is on my phone, but my wife's phone has USB-C and I have 9000 and 1 usbc cables at home.

> Every Operating System has to offer the user the choice of which browser they want to use. Except for Apple, they offer a choice of which UI you want to use, but on iOS the browser engine is always Safari (which kills competition hard on iOS devices).

This is due to security imposed on App Store apps: can't do JIT, and you can't have a reasonable JavaScript engine today without it. Frankly, I'm not concerned with what engine browser uses as long as everything synced.

I have plenty of annoyances with Apple, but what people usually bring up are from people just looking for reasons to hate on Apple for no reason.

Actually, I prefer wireless charging as well (started with my Samsung S3 around 2014), in part because I can use the same charger for Apple as well as for Samsung, but also because they have no wearout and I don't like cables. However, the point is, that all manufacturers had their own adapters in the past (pre-2007) and all but Apple switched to Micro USB and later to USB-C (because the law demands it). So if Apple would also have switched to USB-C we wouldn't have the discussion.

> I'm not concerned with what engine browser uses

Just to give one example from the top of my head: For years (5+), Apple did not implement a proper Push-API for Safari. All other major browsers had it, but because on iOS all browsers are just Safari, there was no way to have it on iOS, which is a pretty big market share. Push-API sound like some marketing stuff, but in reality it is pretty fundamental to a lot of use-cases like multi-user synchronization, chats, etc. So you might think that you don't care about the rendering engine, but in reality Apple can abuse the browser situation to control the whole JS ecosystem.

So I don't hate Apple for no reason. Instead, I hate them for very specific reasons. They also do good stuff (primarily for their users/customers), but for me the bad far outweighs the good, because it affects everybody who has contact with their customers and not just the people who decided they want to have an Apple device.

> All Smartphones on this planet use the same USB-C charging port except iPhones. And as far as I remember, the European Union requires the manufacturers by law to use USB-C, because before the law every phone came with a different power adapter.

The law you're talking about here specified that the charger itself must have a standard USB-C port. Apple gets away with it because 1. they don't even bundle a charger anymore, and 2. they ship a cable that allows the phone to be connected to a USB-C charger (Lightning to USB-C cable).

The new law that takes effect some time in 2024 for smartphones (amongst other devices) stipulates that the port on the smart device must be USB-C. Under this new law, essentially if a device is large enough then the port must be USB-C.

> Next example, OS and browsers: Every Operating System has to offer the user the choice of which browser they want to use. Except for Apple, they offer a choice of which UI you want to use, but on iOS the browser engine is always Safari (which kills competition hard on iOS devices).

Another new EU law (the Digital Markets Act) takes aim at this specific issue actually.

I get where you're coming from, and yeah sure one could argue that giants like Apple, Google, Microsoft should do better, but in the end they are corporations who will do what is best for their shareholders, as such I am not in the least surprised over actions they take like the ones discussed in your comment and the article that started this discussion.

I think it's great that governmental regulation is finally coming to set the game rules for things like how general purpose operating systems must allow device owners the ability to install their own software (including real actual browsers with their own engines and everything), how communication apps must support cross-network communication upon request, and to standardise how we charge our smart devices.

Thanks for the details.

For me it shows what kind of a company Apple is. Even companies like Sony (who install rootkits on your devices without your consent), comply with the spirit of the charging adapter law. But Apple tries to find a loophole, just to push their own agenda, at whatever cost for society.

But as you said, the other large corporations probably do it in some way too.

One could argue that the spirit of the law is an aim to reduce e-waste, and changing iPhones to USB-C will render literally billions of Lightning to USB-A/C cables useless within a few years. But there's obviously the argument that the existence of a need for those cables is in itself a source of e-waste production...

I swing both ways honestly, I love many engineering aspects of the Lightning port, and at the same time I recognise that having only USB-C to care about would obviously simplify my life a bit, even if I think for the purpose of a mobile phone it is an inferior port.