K
Kerryd
Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: imap
I was reading the thread on sync services not working in Mactopia and came across the following post which I went to respond to and found the thread was closed. Its odd as the topic is still totally relevant. Anyway, the post I was going to respond to was posted in Jan 2009 and is:
Re: iCal sync does not work in Entourage 2008 Print This Reply
It's been almost an entire year since this thread started and basic sync is still as much of an issue as day one- read the first few posts, then read the latest few. The MVPs on this forum are well-intentioned but clearly have no ability to make a difference in this product. Feedback to Microsoft has been provided, but still no fixes.
Within hours of installing Mac Office 08, I downgraded to Entourage 04. Many months later I am still cleaning up the mess it wreaked on my devices. I will not approve additional upgrades for the rest of our organization until sync is fixed. (We reached a similar decision regarding Vista and will not approve additional OS upgrades until Windows 7 demonstrates better stability)
All too well I understand the impossibility of pleasing everyone, but when a very capable and well-funded development team is encouraged to focus it's resources in 'improvements' in UI design, then evidential functionality will likely suffer.
Syncing is complex and not trivial to pull off between multiple OSes and numerous applications. However, there are API's defining the elements and processes. And please remember that Mac Office is a Mac product designed to run under Mac OS. The onus is on the developer to follow the host OS guidelines and APIs. Trust me, Microsoft won't support developers or certify products for their platforms that don't follow their rules. Mac Office sync services do not adhere to the defined APIs. Who's the developer, in this case? In a reversal of usual roles, it's Microsoft. They need to follow the rules, or at least break them with no ill effect to the product's functionality.
Cutting thru all the reasons and explanations offered by Microsoft spokespeople and other posters here and elsewhere, what REALLY is the problem here? Why is this still not adequately addressed after more than a year? I tend to believe that Microsoft simply didn't feel syncing was as important as interface improvements for mainstream users. At the time priorities were being set, syncing may not have been considered mainstream, and numbers set priority for product development.
Perhaps more rapidly than expected, the user environments are becoming more and more dependent on multiple platforms for their daily functionality - just scan this thread for a glimpse. Therefore, the need for reliable sync services have quickly become more mainstream.
If my assumption is true, and now that it's been over a year since release and the number of people needing reliable sync services has grown rapidly, then I would hope there can be momentum toward fixing the issues. The time for excuses is long past - it's time for fixes.
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: imap
I was reading the thread on sync services not working in Mactopia and came across the following post which I went to respond to and found the thread was closed. Its odd as the topic is still totally relevant. Anyway, the post I was going to respond to was posted in Jan 2009 and is:
Re: iCal sync does not work in Entourage 2008 Print This Reply
It's been almost an entire year since this thread started and basic sync is still as much of an issue as day one- read the first few posts, then read the latest few. The MVPs on this forum are well-intentioned but clearly have no ability to make a difference in this product. Feedback to Microsoft has been provided, but still no fixes.
Within hours of installing Mac Office 08, I downgraded to Entourage 04. Many months later I am still cleaning up the mess it wreaked on my devices. I will not approve additional upgrades for the rest of our organization until sync is fixed. (We reached a similar decision regarding Vista and will not approve additional OS upgrades until Windows 7 demonstrates better stability)
All too well I understand the impossibility of pleasing everyone, but when a very capable and well-funded development team is encouraged to focus it's resources in 'improvements' in UI design, then evidential functionality will likely suffer.
Syncing is complex and not trivial to pull off between multiple OSes and numerous applications. However, there are API's defining the elements and processes. And please remember that Mac Office is a Mac product designed to run under Mac OS. The onus is on the developer to follow the host OS guidelines and APIs. Trust me, Microsoft won't support developers or certify products for their platforms that don't follow their rules. Mac Office sync services do not adhere to the defined APIs. Who's the developer, in this case? In a reversal of usual roles, it's Microsoft. They need to follow the rules, or at least break them with no ill effect to the product's functionality.
Cutting thru all the reasons and explanations offered by Microsoft spokespeople and other posters here and elsewhere, what REALLY is the problem here? Why is this still not adequately addressed after more than a year? I tend to believe that Microsoft simply didn't feel syncing was as important as interface improvements for mainstream users. At the time priorities were being set, syncing may not have been considered mainstream, and numbers set priority for product development.
Perhaps more rapidly than expected, the user environments are becoming more and more dependent on multiple platforms for their daily functionality - just scan this thread for a glimpse. Therefore, the need for reliable sync services have quickly become more mainstream.
If my assumption is true, and now that it's been over a year since release and the number of people needing reliable sync services has grown rapidly, then I would hope there can be momentum toward fixing the issues. The time for excuses is long past - it's time for fixes.