Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Fire your email and/or network admins. I'm serious. I only receive a couple hundred emails and send a few dozen, so maybe I'm not a heavy user like you are, but I literally can't remember the last time Mail.app crashed. It's always worked, day in, day out, and without failure.

I don't think so. We're a large Microsoft consultancy. We have 2 certified exchange admins who know their shit. it's not misconfiguration. One is an Exchange MVP as wlel. This is a regular problem with all iOS devices connected to Exchange. We've had a large insurance company who is a client ban all iOS devices as well due to this issue. They've switched to Android.

> All the recent "iphone won't play mp3s" query hits were problems with iTunes Match. I absolutely agree that it's had its issues, but it's been running smoothly for quite a while.

Look harder.

> I guess I didn't. So it's like one of the apps listed at http://wiki.openstreetmap.org/wiki/Apple_iOS#Navigating_feat.... then.

Absolutely nothing like any of them. I've spent about £200 on iOS navigation apps and nothing comes close. Only a real piece of dedicated hardware is anything like it for accuracy and reliability.

> "My mailserver is obviously misconfigured because I'm having symptoms that almost no one else is describing. I shall blame my phone vendor."

This is not a mail server issue. By elimination, Android devices, Windows Phone devices, Blackberries, Outlook on desktop all work fine. The only odd one out is iOS.

This is surprisingly common. Most people just don't talk about it as they don't give a shit or don't get annoyed by app crashes etc. They assume that's the status quo, then shout at their ops team who sort it out.



> I don't think so. We're a large Microsoft consultancy.

Color me surprised ...


We're also an oracle java certified and redhat certified and VMware certified and more of our kit is on Linux, so it's not biased :)

My point is that we're citably competent all the way through.


In my experience, there are two kinds of people:

1) People who don't use the Microsoft technology stack.

2) People who use Microsoft's proprietary technology stack, and then get annoyed at products that fail to interoperate with it seamlessly, despite the fact that it's undocumented, proprietary, and notoriously difficult to interoperate with successfully.

There are very few people who use MS stack and don't get annoyed at interoperability concerns, because those people realize that the fault lies with Microsoft, and stop using Microsoft's stack.


oh come on...




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

Search: