4 ms·
A few things to note about Apple & Apple users: 1 - Apple doesn't focus on "first". More often, they are usually focused on a better integration of something t
by MR4D 6y ago
A few things to note about Apple & Apple users:
1 - Apple doesn't focus on "first". More often, they are usually focused on a better integration of something than being first. Obvious exceptions include things like 64-bit phone chips, but usually not first.
2 - most Apple users (note that I am saying users, and not developers or power users) prefer it that way. They prefer simplicity over raw power - sort of the revers of a linux command line user.
3 - Even the power users tend to like something that keeps them in the Apple camp. For me, it's the ecosystem an approach to privacy and security - I can help my parents be safe easier on an iPhone/iPad/etc than I could on an Android phone.
4 - For many (most?) people, the apple email app is better than most alternatives. Personally I run gmail, outlook, and apple, and prefer Apple in most situations (not all, but most). Think of this as "I can't believe that Lexus doesn't have an electric car yet" - most Lexus users don't really care because they are happy with the product as is. Would some subset prefer it? sure, but not enough to outweigh the reasons they bought the Lexus in the first place.
5 - I'm not an Android user, but I agree - it is a funny headline in 2020.
- xwowsersx 6y agoOh I totally get all of this and I agree that it's fair to characterize Apple's bent as being UX at the expense of user freedom and that many people _specifically want_ this, but at this point it's overstated as applied to some of these features. For example, default browser - Apple doesn't need Android's complicated system whereby you choose whether this app opens up links of a certain type always or just this once, etc. Apple could just have a setting where you choose your browser. Unless I'm just naive, this should add no overhead in terms of UX. Same applies to email client.
- MR4D 6y agoI wonder[1]. Not disagreeing, and I'm not a systems programmer, so I can image that there are aspects of things to make something truly secure[1] that you have to chase down all these rabbit holes. I look at OpenBSD and see how long it takes them to do something fairly "simple", and use that as a guideline for security development integration timeframes. Of course, OpenBSD isn't backed by a trillion dollar company either. Oddly, I fall into the Mac + Linux camp. I love using MacOS (yes, even Catalina works for me), but I love that doing development/server stuff on Linux is so clean. What both do for me is minimize the brain clutter (and that's one reason I can't grok the idea of doing server development in Xcode). [0] - I don't think you're being naive. Also, being a fan of guys like Krebs on Security makes me realize that doing this right is not so much hard as it is painstaking. [1] - no, I definitely don't think iOS is totally secure, but I think it's harder to screw up as a user than competitors.