No. I'm saying that the reality distortion field is strong. It's slowly fading now, but you can't deny it was quite impressive when Jobs would announce something everyone else had for ages and because it was Apple doing it all the fans who previously said they didn't want it were suddenly sold on the idea.
Yep, that happens -- not just for iOS, but for any platform for which there is a loyal fan-base. For whatever reason, products tend to spawn zealots, and Apple's marketing milks that for everything it's worth. Even with more reasonable folk, there are biases. That is without question, and it is indeed irrational. I'd like to say I have none, but I do... and so does everyone else. Human nature. What can ya do.
I'm just saying that you don't seem to objectively evaluate features or functionality because even when there are better alternatives you prefer the Apple version but can't state exactly why beyond a vague "I just prefer it".
Perhaps I just haven't asked directly enough. What, specifically, about the way the iPhone works do you prefer?
I am not likely to provide an answer that is going to satisfy you. Take an iPhone and an Android phone side by side. They both make calls, they both send/rcv email, they both run apps. There is effectively zero difference in basic functionality. The majority of the differences are in the user experience, and mobile devices are very personal.
You clearly value your freedom to share data between apps and get software from various sources. Great. I do (and have) admit that I would like that too, but I find that I'm rarely encumbered by those limitations in practical use, so I'm willing to accept them. The flipside of that is how the OS "fits" my personal tastes. There are a ton of little things that mean practically nothing in isolation -- lots of it being aesthetic or otherwise qualitative -- that add up to make iOS preferable to me. A lot of it is even subconscious.
Take, for example, the behavior while scrolling. You get to the end of a list, and iOS has that little bounce effect instead of stopping sharply. Or, when you rotate the screen, the content pivots smoothly around the center instead of falling over like a block. Back in the earlier days of Android, these things made iOS feel a lot more polished. It's stupid and insignificant, but it's exactly the kind of thing our minds pick up on and react to in ways you can't think your way around. It's as elemental to usability as learning to catch a ball and understanding the physics of gravity. It feels right. There's a reason Apple fought to keep those stupid effects proprietary. I have no doubt they spent a lot of time tweaking that stuff. The human reaction to that stuff has huge consequences.
The hardware is the same way. The device feels nice to hold. The voice quality has always been really good. I've heard a few other phones that I thought sounded like crap. Same with the speakerphone. I've used Motorola phones and BlackBerries where the keys wore out. I've had three iPhones now (two personal, one work) and they worked perfectly until I was ready to trade up for other reasons. The screens look great. Say what you will about Retina, but I don't see pixels unless I look really, really, really closely. The color and contrast are very good. So is the camera quality. (All for its time, of course.) In contrast, around 2010 when I was moving from a 3GS to an iPhone 4, every Android screen I saw looked bright and sharp, but a little oversaturated and had a bit of a green tint that I didn't like.
I don't remember if I already gave this example, but I recently sat down with a coworker that just moved here to show him where some place in town was located. I couldn't figure out how to get into Street View on the Google Maps app. Also an iPhone user, he echoed my frustration: "Oh I know.. the old Maps app was better. Come to think of it, I can't remember how you get to Street View either." We tried a minute or so, then gave up. I just pointed him to some nearby landmarks that he knew. This isn't crucial, and I can Google it or keep tapping around to try and find it, but (at least pre-iOS 7) that sort of thing just didn't happen. I never had to
learn how to use the native apps, they just made sense. I'll accept learning curves for things that should take some effort, but this just isn't something that should take time to figure out.
Those things all matter, and add up a hundred little tiny stupid insignificant quirks and the end result is, I
like the iPhone, and I have not, to this day, held an Android device that I like
as much. You don't have to agree here. That's why Apple exists alongside Google and Samsung and HTC and .... You don't even have to understand or think my reasons have any validity. Just try and get that it has nothing to do with trendiness of the platform. I really have no interest in following the pack. I don't use Facebook, and the only name-brand clothes I own were popular 15 years ago. No one is going to accuse me of being trendy -- until I mention I use an iPhone, and then it's "OMG sheep!"

It gets old.
Anyway, I'm sure the hardware landscape has changed dramatically in the last four years, but that was the last time I shopped for a phone, so aside from a few quick comparisons when an acquaintance got a new phone and offered a quick demo, that's all I have to go on. I tell you this -- I was looking hard at the Atrix last time, but I ended up staying with Apple because the Android OS seemed a little rough and sloppy at the time, and the big selling point -- the laptop dock -- was too expensive to be a realistic alternative to just buying a netbook, which would've performed better anyway.
Now, I'm ready for a hardware upgrade again, and so I will hold one of the new enormous and pliable iPhone 6s and whatever comparable Android phones are there. I might be won over by the competition, especially since I'm a little unsure about the new iOS, and the new big and thin 6/6+. But it will have to
actually win me over, as I see no point abandoning a platform I'm content with for a lateral move.
That said, Cyanogen looks interesting. I don't know anyone running it, and since it's probably not available for demo at the local phone store, I dunno if I'll get around to giving it a fair shake this time around. But I will definitely be keeping my eyes open.
It's not all roses though. When I gave up my flip-phone for the 3GS, I was shocked to find that this new fancy thing couldn't move pictures and audio files back and forth via Bluetooth. That has been resolved by other means (e.g. WiFi transfer), except that you just can't export stuff from the local media store (i.e., what you put on the phone from iTunes). That might be an unavoidable condition of being highly visible in the media market. I get around that by using 3rd party apps for transferring audio and video to and from the device. NBD.
SD card storage would be nice. Although with 64GB+, I can store my entire music library, all the apps I want, selected movies when I travel, and have enough room left over for pictures, video, email, and OS updates. My current phone (32GB) is a bit limiting in this way, but we share an iPad with 64GB, and storage has never been a problem. The iPhone 6 has 128GB available. At that point, I don't think I would even use external storage if it
were available. I do not dispute that the high-capacity models are overpriced for the storage you get. It's good to be king I guess... I sigh, and roll my eyes, but ultimately, I can afford it and it's worth it to me. When you think about it, $700 is a pretty cheap computer actually.
Next complaint: I hate iTunes and the limitations on importing and exporting media. I've gotten around that by encoding mobile versions of my movie collection (which I would do anyway -- I don't want to dedicate 20GB per film on a phone) that
can sync via iTunes, or just using one of the many SMB-compatible apps to copy movies into local storage. It's only accessible in that one app, vs. the more open file system you'll get on Android, which is a shame... but again, it doesn't affect my usage much. There is limited sharing of data between apps, and hopefully they'll eventually loosen up and provide a little more filesystem visibility. Until then, I have methods that work, so... meh.
But that isn't what the iPhone has. The laptop displays are slightly better, but the crap font rendering in iOS doesn't help them.
(Quote) It's generally understood now that when someone says "Retina display", they're referring to a high-DPI screen that has sufficient resolution to render curves without obvious stepping. ... Whether you agree that the DPI is sufficiently high to meet that criteria or not is irrelevant.
It was your entire point in the previous sentence.
I have no idea what you're talking about WRT font rendering quality. Looks fantastic to me. Concerning the second point, Retina refers to high-DPI screens that do not visibly resolve pixels. You're obviously free to disagree that the DPI is high
enough. That's still the point of the phrase, and I agree with it in practice. I really have to strain to see pixels, so to my eyes, they're not resolvable from ordinary distances. Could be you just have exceptional eyes. Or it might just be your bias. Whatever. *shrug* Higher DPI panels exist, so you're covered either way.
You mean the second gen iPod Photo? There was never any device called an "iPod Video" according to Wikipedia, but it could be wrong. I thought it was just the 2nd gen Photo though.
No. On Wikipedia, it's labelled iPod 5th Gen. I dunno if it was ever officially called "iPod Video", but it was colloquially known as such if nothing else. Great little player. It was a gift, since I had been reluctant to get an MP3 player... I hadn't found anything I liked. I showed some interest in the iPod, so my SO bought one for me, and I l-o-v-e-d it. Carried it everywhere, literally. Permanent fixture in my pocket, along with a wallet and flip-phone. That device changed my opinion of Apple. I was a hardcore PC guy, and would've preferred something from Creative Labs (also really fond of the SoundBlaster line from years previous), but as I said before, their player was nothing compared to the iPod.
Interesting to hear about the older, inadequate analog output stage. I dunno what to tell you. Like I said, I got onboard pretty late, and the one I had sounded great to me. I also watched the entire first season of BSG and Lost from that thing connected to a TV. No complaints on quality whatsoever. Video sure wouldn't hold up today, being SD and limited decoding capability. But for audio playback, even with my Sennheiser and Sony over-ear headphones, it sounded good. I sometimes did max out the volume, but it's a portable device. I expect as much. None of my Discmans or Walkmans (or clones thereof) ever blew my hair back in that regard either. A few specialty players do have high-current output stages meant for low-impedance headphones, and I'm sure they sound slightly better. But, good enough is good enough for a mobile audio device. And the iPod sounded plenty good enough to me.
The key difference is that when Sony was making those machines no-one else offered anything comparable. Now the Air is basically okay but overpriced compared to the competition. I suppose if you must be iOS then it is your only legal option, but for Linux there are much better and cheaper machines out there. NEC's ultrabook range, for example, is just as thin but lighter, has better screens and more powerful hardware, and they are easy to maintain.
I haven't ever seen the NECs. Saw a few Samsungs, and got a chance to use one of the larger ones. It was OK, I remember hating the keyboard, but I don't recall why. The later Sony stuff has a design aesthetic I don't like as much, and it got to the point where they were just as unrepairable and unupgradebale as an Apple device, so.. eh.. Using a Dell Latitude now because I got to keep it when I left my last company. Too big, but it works.
In what way is "insert device, wait for driver to install" elaborate? .... That was true back in the Windows 98 days, but not any more. Even as long ago as XP, 12 years ago, it wasn't true.
It's not elaborate from a user point of view -- when it works. But the mechanism for installation is overly complicated, and prone to error. Yes, still. MS and vendors both try to shield users from this to varying degrees of success. I had the pleasure of being a desktop admin for a large company for a while. Local (USB) printer drivers are the worst. Then you see stuff like "DO NOT PLUG IN YOUR DEVICE until installation is finished!", and "This driver is not signed, continue anyway?", and so on. I have personally had to sit down in front of a computer and download utilities from a device vendor to fix problems because the user made the mistake of plugging in the device first, and then trying to install the software on the included CD. This is admittedly a relatively rare problem, but it possible because of a very poorly designed driver framework. Part of my living has come from the fact that this is a truism.
In contrast, we had one remote site that used Macs exclusively, except for couple of Windows PCs we sent them for compatibility with certain business apps that we mandated they use. For some reason, they also tended to use the PCs for email -- no idea why, since Office was available for Mac. I think it had something to do with the local network there, but whatever. Point being, we never heard a peep about the OS X machines. Those user were completely self-sufficient unless they needed something (like new software, or a new copier, etc.) It could be they were all just really smart and savvy, or it could be that OS X is good at letting the user do their thing w/o getting in the way.
Since this particular subsidiary was a graphics shop, let me harp on printer drivers for a moment more here because they truly are the worst. Our IT director tried to come up with some sense of standardization (only PCL... no, only PostScript.. OK, except when the copier has a preferred native driver... OK, just do whatever you have to do to make the thing work) -- but to no avail. Now, MS dominated (and still dominates) the business market. That's an area they could've exerted some force and cleaned up the mess. We never had to touch the OS X printer drivers though.
Similarly, Apple comes along with this little thing called AirPrint. You walk in with an iOS device, see something on the network that speaks AirPrint, pick it by name, and print. That's it, you're done. There's NO set up ahead of time. Now, it hasn't taken over PostScript exactly, but it is completely effortless on supported devices. We had a bunch of executives carrying iPads after a while, and this made life really easy for us during annual meeting time. We kept one printer in the conference room that spoke AirPrint, and our maintenance pretty much just ended with keeping it filled with paper and toner.
PostScript has the PPD specification to tell the host everything it needs to know about the printer to send it a job. It's a small leap to work with manufacturers to include this in a printer's ROM and come up with a standard USB class driver to make thing whole thing seamless. Similar functionality could be achieved over a network by standardized queries. In other words, Microsoft could have, in its position of authority, pushed for AirPrint-like functionality ten years ago. Or, a generic interface where clients print to the Windows print server, and only the server has printer drivers to worry about. (Now, you provide drivers at the server, but the client still has to download and install them.)
This is a very specific example, but I hope it illustrates the kind of issues I have with the Windows driver ecosystem.
On a similar note, go to Google Images and compare "OS X System Preferences" to "Windows 7 Control Panel". Now imagine you have to walk a customer or your parents through one or the other. One of my first tech jobs was at a DSL help desk. Win98's IP stack was clumsy, but at least the steps to get to network card and protocol settings were simple. When XP came out, it was a little more work, but still bearable. After I left, I talked to some folks still working there when Vista came out. They HATED it.
When we got Mac calls, all you had to do was look at some screen shots once. It's a direct route, and I don't remember if I ever got a call where it didn't work. I walked a lot of Windows users through resetting the IP stack though. Similar with field visits. Lots of Mac homes, but the only reason I was there was to install the service. I had no end of PC repair calls. The numbers are skewed, since there were more PC users than Mac users, but I knew when I got to a site where they were using a Mac, I was going to be done in five minutes. On a PC, I just expected I would need to find and install a driver, remove a dozen IE toolbars, run Windows Update to fix some known issue or other...