Or he hates it. I've used Exchange, and the main reason I'd have written this about GMail instead of Exchange is that Exchange does too many things, poorly. I

Or he hates it. I've used Exchange, and the main reason I'd have written this about GMail instead of Exchange is that Exchange does too many things, poorly. It's fine for email, in the sense that I would never use it for personal email and I don't care if it occasionally loses a piece of work email. But its scheduling makes its email processing look reasonable, in that it only occasionally loses a random piece of email, but it loses schedule items constantly. This is, again, fine, because I only use it at work, and so when you say "Exchange lost it", you're surrounded by sympathetic people who constantly have the same experience. If I were, say, running a startup, I would actually care about not having my email system lose things constantly, and so I would avoid Exchange scrupulously. I mean, maybe it's just been misconfigured in two or three large companies where I've worked? Misconfigured by professional system administrators, who don't hate configuring Microsoft products the way I do? If so, then it's hard enough to configure that I should never do it for myself. I'm a good programmer, but only an indifferent Windows admin. For all of these reasons, it's possible that the OP didn't want to imply that "Exchange is solving the right problem" when he could instead be saying "GMail is solving the right problem." If it were me, that's what I'd be doing.