Slashdot Mirror
VBA Will Return To Mac Office
An anonymous reader sends a pointer to Erik Schwiebert's blog — he's the design lead of Microsoft's Mac Business Unit — where he announces that Visual Basic will be returning to Mac Office. Not in Office 2008, which started shipping earlier this year. We discussed the announced death of VBA in Mac Office 17 months back. Schwiebert says that the interval to the next version of Mac Office will be shorter than 4 years but isn't able to offer any more detail. The blog post calls for feedback on what features of VBA and Windows interoperability are most important to people.
Shorter than four years? Now there's commitment to a schedule!
You never know, by that time ODF might be a highly used standard, Linux and Mac might have dwarfed Windows, and MS Office might have been replaced in a lot of office environments.
...already has support for it.
That is just _so_ cool. I'm absolutely dying to help my customers by creating cross-platform applications in VBA. They will enjoy all the goodness and richness of the Microsoft Office platform, with 86 MB single-user OLE files, spreadsheets/graphics/mail-merge/database-monster all rolled into one. On a share. So everyone can use it.
8 of 13 people found this answer helpful. Did you?
Question is why they dropped it in the first place?
My personal bet is that they wanted to Office on Mac look less business like. That would stop Macs going to enterprises where (as everybody knows) MSFT has a nice profitable stronghold.
"an experienced, industrious, ambitious, and often, quite often, picturesque liar" - Mark Twain
Features are important? How about making it so some middle manager can not make some MS Access app and then have upper management have you deploy it for 100+ users to use.
The number of fricking POS Access applications I had to support that were coded so badly that it took days to figure out what the person was trying to do is insane. Corporate america is riddled with these kind of monsters causing IT people to ball up under their desks and cry through the night.
I was happy when they removed VBA because it stopped that nightmare.
Do not look at laser with remaining good eye.
I think the reason they gave was that it was too hard to port the old Office 2004 VBA runtime from PPC to x86 code - the runtime was apparently an absolute mess that was tied very tightly to the ISA. Why they didn't write one portable VBA engine for Windows and Mac I don't know.
Whether that's true or not I don't know, it's the old choice between assuming incompetence or malice I guess.
Wasn't it just a few weeks ago that the OpenOffice 3 announcements were made, including partial VBA support for the Mac version? Microsoft seem to be happy to drop VBA support from the Mac version to try to persuade people who rely on it to switch to Windows, but to add it back when that reason no longer applies, so as not to lose marketshare to the reason that it no longer applies... (And yes, there were other office suites that could do that beforehand, but businesses are at least likely to have heard of OpenOffice.org/StarOffice.)
(1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
Access? You're lucky those folks in my company uses Excel for their databases and labview for hardware control and DAQ... It's like watching a train wreck on herion.
Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
There is simply no compelling reason for me or my organization to deploy the new version of Office - why spend thousands for new licenses (and associated deployment and support) when I can stick with the tried-and-true 2004 and just wait a couple years for "Office 2010"?
I find that Office 2004 is quite a bit faster than Office 2008 on my Intel-based MacBook. I'm not sure what they did to it, but it isn't impressive in terms of performance. You'd think that converting from translated PPC code to native x86 code would be a huge performance advantage, but somehow the Microsoft managed to slow it down quite a bit.
Oh, and Office 2008 has fewer features, like no VBA.
What was Microsoft thinking during design and testing? Clearly they have totally lost focus and ability to release a decent product.
Visual Basic will be returning to Mac Office.
What did Mac users do to deserve that punishment?
That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
MAC: Hello, I'm a Mac.
PC: [surrounded by noisy children] Hello, I'm a PC. Ha ha ha!
MAC: PC, it's good to see you laughing. Who are all your friends?
PC: [children are poking and pinching PC] Oh them? Ouch! Ha ha ha! They are Script Kiddies! Ouch! Ha ha ha!
MAC: Script Kiddies? What do they do?
PC: Now that VBA, the Enterprise Virus Development Platform, will soon be available on Office for Mac, you are about to find out. Ouch! Ha ha ha!
Rich And Stupid is not so bad as Working For Rich And Stupid.
Probably because VBA was introduced around 1993, the same year the first Pentium (running at 60MHz) was introduced. The typical machine had a 486DX2 running a single instruction pipeline at 33MHz, and maybe 16-24MB of RAM. Oh, yes, and Windows 3.1, which is 16 bit and has all its 16 bit glory.
Still, C code can be reasonably close to assembler in efficiency, especially if you profile and use assembler only in tight loops. It shouldn't be that hard on modern systems to cross compile to C against some kind of simple virtual machine.
I'm guessing that the code probably makes a lot of direct Windows API calls without any framework or abstraction. This probably means that collectively the VBA code for MacOS and Windows is significantly larger than for Windows alone. If this is true Microsoft would have to port a lot of the Windows API to MacOS (nobody is better positioned to do this), or they have to do a rather massive refactoring. Since porting the API is undesirable for other reasons, and refactoring is desirable for others, I'm guessing they're planning on cleaning things up enough to make a Mac port viable.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
With NeoOffice and OO.org many Mac users already feel we have no more need of MS office. In four years' time, that will only be more true. The end of MS' monopoly on business software is definitely in sight now, and they brought it about themselves with their greed, over-confidence, and short-sighted policies.
It wasn't so long ago I pretty much had to use MS software on my Mac to do all I needed to do -- WMP, Office, IE. Today, the only MS code on my Mac is codecs for wmv and wma files (which I play in mplayer). This is real progress, and we owe a big debt of gratitude it to the FOSS guys.
Caveat Utilitor
No kidding. I'm actually a paid Office:Mac user (albeit a previous version) and I still use Neo Office. Other than being slow to load, it does everything I want it to, and it's free.
Unless you have some special need for Microsoft Office that Neo Office doesn't meet, I don't see any reason to pay for Microsoft Office other than just not knowing any better.
www.clarke.ca