Despite 4 years of development on from Office 2004 it's only really gained better performance on Intel. It's still full of bugs and doesn't support Exchange, or Office 2007 documents properly. Removing VBA makes Excel next to useless.
If 2007 is buggy I haven't discovered them yet. Office 2008 has shoved the bugs in my face and made then quite obvious.Only really gained support on Intel? Open your eyes, man - there is tonnes of improvement.
It's buggy, but just as buggy as Office 2007 on Windows is.
Rich
If 2007 is buggy I haven't discovered them yet. Office 2008 has shoved the bugs in my face and made then quite obvious.
Do you want to go into the improvements or just tell me to open my eyes? It loads slower than 2007 on Windows, and doesn't really bring anything new to the table, whereas 2007 took the gamble of redesigning the menu system totally, and it paid off.
The #1 objective of the Mac version of Office should be total compatibility with the Windows version - without this you might as well use anything that can open .doc files. By removing VBA and having different ways of processing images stored within files Microsoft ignore the only "must-have" reason for buying the product.
The biggest slap in the face is Exchange support, so many people thought 2004 was just a blip and that with another four years of development Mac users would finally get a level of Exchange support that they haven't had since Outlook 2001. Once again, this hasn't happened.
How Microsoft can call it an Exchange client with those glaring omissions is a joke.A number of features users have been clamoring for—including syncing tasks and notes, the ability to manage Exchange Server Rules and to import and export personal folder files (PSTs), better integration of Exchange categories, and Distribution List management—are still undone.
The redesign of the Mac Office isn't the ribbon, it still relies on nested menus. The "fake-ribbon" is just for picking a style, and takes up far too much space while it's doing it.
That's Apple fault because MS had to follow the design principles set out by Apple that meant the ribbon was off the cards. Also, the VBA thig is not that big of a deal because MS are dropping VBA completely when they move to the next version of Office becuase they aren't porting it to a 64bit code base.
My point is that the only real reason to use Office on the Mac over one of the many alternatives that can open Office documents would be for 'native' support. Having things which you can put in a document on Office 2007 which don't work when you open it on the Mac makes that reason disappear.That's Apple fault because MS had to follow the design principles set out by Apple that meant the ribbon was off the cards. Also, the VBA thig is not that big of a deal because MS are dropping VBA completely when they move to the next version of Office becuase they aren't porting it to a 64bit code base.
I wonder what all the VB programmers are going todo?? Hopefully curl up in a ball and shrivel up.. Nasty, despicable - bleugh!
I suppose it will be C#
The redesign of the Mac Office isn't the ribbon, it still relies on nested menus. The "fake-ribbon" is just for picking a style, and takes up far too much space while it's doing it.
Bugs in 2008, where shall I start? I'd say the most obvious one is that none of the underlined blue text in the interface actually does anything when clicked on. For years we've been taught that underlined blue text is a hyperlink, but in Office 2008 apparently having a phrase such as "Preferences dialog box" presented in this way actually means "go and find it yourself". Then there's the utterly broken interface in Entourage where navigating between the Calendar and Inbox can break the buttons unless you do it in the correct order. These are basic things that should all have been picked up before release.
Please try and use their "Exchange support" before claiming that I'm wrong. It is not a MAPI client like Outlook is. It relies on using Web Access, yet somehow manages to support even less.
This overview explains it well:
http://www.macworld.com/article/131730/2008/01/msftexchange.htmlHow Microsoft can call it an Exchange client with those glaring omissions is a joke.
They aren't dropping VB just VBA. VBA is special implementation of VB inside Office and a few other MS apps. VB .Net remains unaffectected
Please try and use their "Exchange support" before claiming that I'm wrong. It is not a MAPI client like Outlook is. It relies on using Web Access, yet somehow manages to support even less.
This overview explains it well:
http://www.macworld.com/article/131730/2008/01/msftexchange.htmlHow Microsoft can call it an Exchange client with those glaring omissions is a joke.
Do I miss not being able to set server rules using Entourage? Yes, it's a pretty basic thing. Do I miss being able to read the notes I've made in Outlook or in OWA? Well, yes again. The same applies to tasks. These are not basic features which are missing by any stretch. But above all I miss being able to connect to Exchange servers which aren't running Outlook Web Access - there is no way to use Entourage with Exchange unless OWA is enabled - it doesn't even support the far more useful RDP over HTTP for remote access.
If I have to have Safari tuned to OWA while using Entourage then I might as well save myself the money and just use that.
I mean RPC over HTTP, which it doesn't support. It only supports being a frontend to OWA.