3 ms·
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'
by 0x457 4y ago
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.
- arendtio 4y agoActually, 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.