MS Office for OSX? Why not for Unix as Well?
technode asks: "Apple
has released OSX, which appears to be an amalgam of NetBSD, and
NexTStep, and other stuff. There is, or will be, undoubtedly, a
'native mode' office suite for OSX. If there is an Office suite for
OSX, then why not for other Unixes? To do it once requires solving
the basic problem of mapping Office onto the Unix/X-windows API. Once
you have that piece, it seems like the only thing preventing a Linux
MS Office Suite is MS desire to preserve their OS market share. Technically,
this begins to seem a little bit like using one's market share in the
applications business to protect one's market share in the OS
business, which would, on the face of it, seem to be an anti-trust
no-no. What gives?" Most people don't seem to understand that
"native-mode" OSX isn't necessarily Unix compatible. Macs have had their own GUI toolbox for a long time, and I would assume that if
Office does show for OSX, that it would be an easy port to
other Unicies. This doesn't even go into the horrendous track record
with regards to security that Microsoft has garnered, especially
over the past few years. Does Unix really need Office at this
point? Update: 12/29 1pm EDT by C :The wording above is incorrect. To clarify: an OS X
version of Office would not be an easy port to Unix. Sorry for the miswording, there.
I was one of the beta testers for Office X. They've fixed many bugs since Office 2001 under Mac OS 9 and cleaned up the interface in Entourage. However, don't look for a full *nix port any time soon.
What MS Has done is comply with Apple's new API to the OS. Office X is NOT a UNIX application, it's still a Mac Application. All the code is Mac PowerPC code and uses Apple's "Carbon" and maybe some "Coco" code (but I'm not positive on the last one). It works well, it's fast and it's developed by a real Mac programming team as opposed to the abismal ports of Word 6 for example.
The truth of the matter is, Apple needs MS and MS Needs Apple (whether or not they want to admit it). I do not think that MS will be porting Office X to other *nixes any time in the future.
-- DuckWing
All personal preferences of bloat, security, blah blah blah aside, I believe the primary reason that MS isn't very interested in MSOffice on the Linux desktop is because of product licensing control.
It's far too easy (in MS's view) for software to be copied under Linux. As a class of users, Apple users tend to be "more honest" about paying for their software. Windows users are questions in a non-business environment (heh, but a number of businesses also, really). But with XP, there will be more control over product licensing.
With Linux, they lose all this, or it becomes far harder to maintain. Also consider this issue: Cost of support for MS. With all the different distros available, I tend to think they mind find the cost of support under Linux as not yet being tolerable.
Linux has it's own version of "DLL Hell" in the libraries. With a MS product, it's *generally* pretty safe to force an upgrade of a MS DLL with a new MS DLL. But what about libraries they have no control over? The only way around that is to replicate the seemingly near 500MB of libraries. And then people complain about bloat!
I'm no big MS business model fan, but I find some of their products (Outlook not included) quite usable. I run Linux, OSX, Debian, FreeBSD, NT4, and Win2K here in my shop. I still use Windows/MSOffice for business work, because I have yet to find anything as good as MSOffice for Linux. Sad, but true, from MY perspective. Anyways, in some respects, they're in a lose-lose situation. They can't control the libraries, etc, and when they load their own, people will whine that it takes a full gig to install MSOffice. What's a company to do? Not bother, that's what.
--John
As has been repeated many times here, what Unix really needs is:
...), Microsoft would have to cooperate in the construction of this program in some way.
1] A standard for office file formats
2] A capable standalone import/export program between this format and MS office formats.
The OpenOffice file format looks pretty good to me, but I understand why there could be reluctance among the many other office projects to ditch their ideas (though I think they should anyway).
Having the conversion program be standalone would allow all competing interfaces to the standard file to coexist nicely with each other. My fantasy is that in the final settlement with somebody (US states, EU,
Dara