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.
While Word for Linux wouldn't be a bad thing for the Linux community, I don't think it's the hottest thing needed. There's a slew of word processing programs for Linux, several of which can handle .doc pretty well. Sure, John Q. Public might be more likely to use Linux if he could use Word itself... But I digress.
________________________________________________
suwain_2
Could not agree more in the large, however there a few big differences.
1) Most windows are of 9X variety, where there is no such thing as a root user, thus any exploit, thus any trojan code automatically can do anything it wants to the system. This is repeated on NT where you have to be admin to do lots of things, so many people grant admin to the desktop user (especially developers) -- This is compounded by the fact that NT servers often run as a privileged account. IIS does this so it can do a runas user -- also a prime example of stupid feature to integrate IIS with operating system.
2) Default installs on windows are notoriously over featured a.k.a. insecure
3) There is no chroot command. If you have to have a server running with special privilege, at least the chroot limits the target area for damage available to exploits
4) There are a lot more complexity on Windows. Windows is probably 100 times more complex than Unix in terms of shear numbers of API's, addons, etc. This almost guarantees there will be a signicantly larger number of security holes
5) Windows does not provide the tools that make it reasonably easy to secure it and keep it that way.