4 ms·
Those tools fall down when you connect them to external services - particularly exchange. Mail.App, in particular, was flawed in how it read from exchange serv
by ghshephard 14y ago
Those tools fall down when you connect them to external services - particularly exchange. Mail.App, in particular, was flawed in how it read from exchange servers from 10.7 through 10.7.3 - It's gotten somewhat better in 10.7.4, and I hear most of my remaining bugs have been resolved in ML. Calendar and Address book are fine as standalone tools, but never really (and still don't) cut it as "Enterprise workflow" tools. Microsoft Exchange + Outlook own the calendar work in the enterprise.
The point I was really trying to make was that Apple's recent failings have been their attempt to work with others - they don't understand how to design/deploy/develop internet services. And they don't play (very) well with others.
They succeed best when you stick to their walled garden, with perhaps the one exception that proves the rule being their web browser - which is pretty spiffy on both the mobile and OS X platform.
- fauigerzigerk 14y agoMicrosoft doesn't play too well with others either but you can customize and hack their software. They want you to do that and they make it easy for power users who are not professional programmers. Apple doesn't want that. Apple wants you to use it in one particular way or not at all. Both approaches have their benefits. At least with Apple products you always know where things are. If you open MS Office on a power user's machine you may find something completely unique to that user. It's very useful to them but totally unsupportable for anyone else. Office is the people's Unix shell in a way. Apple doesn't want to be that and it isn't.