Hacker News new | past | comments | ask | show | jobs | submit login

How does 'crashed to reboot twice in a day' convert to 'it's very stable'?

It's this wilful disregard of negatives that bugs me about Apple culture. The good things are lauded, the bad things are ignored, unless they're bad things in other OSes, then they're highlighted as why Apple stuff is better.

It's like at my last workplace, the Apple fan who was always getting another box from Foxconn telling me that Android was crap because he occasionally saw me swipe twice on my phone - ignoring that he was doing the same on his iphone. He didn't realise it until I pointed it out to him that he was doing it. It's a really odd cultural phenomenon.




Seriously? This is the earliest beta of this release. Only bricking twice a day sounds "pretty stable" to me.

I've had an iPhone5 since it came out and I've had one instance of needing to hard-reboot the device. Can't remember the details.

OTOH, My previous phone, a Galaxy S2, had far more issues. Multiple times in my ownership -- at least 4 that I can remember -- I literally had to remove the battery to restart the device.

In many ways I wish I had a hybrid device. The fit and finish of the hardware itself is much better from Apple. Some OS features and especially Google-provided web services are much better on Android. (Speech-to-text for one..) But having owned an Android for 2 years and an iPhone for 8 months, the iPhone is definitely, definitely more stable.

In some ways it seems like Apple v Microsoft on the desktop again. Apple controls the OS and the hardware so yes it BETTER be more stable. And it is.


We seem to be speaking a different language. To me, 'bricking' means you've hosed the system and it can't be recovered without low-level tools. A reboot crash is not 'bricking'.

My pedantometer also suggests that 'pretty stable' and 'very stable' are not the same thing. :)


Before I had an iPhone 5 I used a Samsung Galaxy S which crashed much more frequently on stable versions of Android. I had to remove the battery at some points too to get it to start. I've never owned a Windows Phone so I can't comment on them.

I'm not apart of the Apple culture—I've had an iPhone for about 6 months and before that I used Android for ~ 2 years and had never owned any Apple products aside from a MbP—and I am not disregarding bad things. You've read a single comment of mine which was made in the context of using iOS 7 Beta 1 as a daily user. I've only made comments on iOS in 2 locations on the internet, once on this HN story and once in an invite-only forum. In the forum I listed many things that I don't like at the moment and feel needs polishing.

What's hilarious about your comment is that by a couple of ultra-geeks at uni I was called an Android fanboy because I used my SGS a lot, modded it, etc., haha. It would be hard for you to have been more wrong in your assumption, in regards to me. You will forever find in every group/culture people that ignore bad things and laud the good things, I've seen the same when I used Android regularly and elsewhere.


It would be hard for you to have been more wrong in your assumption, in regards to me.

Speaking of assumptions, I didn't call you a fanboy. I said it was a peculiarity of Apple culture. Given that I only have "a single comment of mine" on which to evaluate, it sounded like so many other comments on Apple equipment, where failures are papered over.

And given that it's a beta, not an alpha, two reboot crashes in one day is still definitely not what I'd characterise as "very stable". I'd even be wary of using that for an alpha - a "very" stable software suite simply shouldn't be crashing that often, regardless of where it is in the cycle.


Can't speak for FireBeyond or dorian-graph but I too am running it on my regular, everyday iPhone 5 and have found it surprisingly stable.

Any actual crashes seem to be a result of doing too many things at once, particularly during an animation (eg: close out of an app and double-click for multitasking before the animation is finished). The crashes seem to cause a restart of the Springbord app rather than a complete system reboot, so it comes back within 10 seconds and hasn't lost any data (it even keeps the same song playing in the background).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: