Slashdot Log In
Microsoft Porting Applications To Linux (Really!)
Posted by
Hemos
on Wed Aug 16, 2000 01:15 PM
from the kicking-down-chairs-and-knocking-down-tables dept.
from the kicking-down-chairs-and-knocking-down-tables dept.
Erbo writes "We've heard the rumors before, more times than we can count, but this time WinInfo claims they're true: Microsoft is working with Mainsoft in Israel and a small French development team to port their apps to Linux, and possibly other Unices. No estimates on availability, of course. Their strategy seems to be to use an "Office for Linux" as a bridge to Windows, similar to Mac Office."
This discussion has been archived.
No new comments can be posted.
Microsoft Porting Applications To Linux (Really!)
|
Log In/Create an Account
| Top
| 616 comments
(Spill at 50!) | Index Only
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Wow, they're... INNOVATING? (Score:3)
It'd be nice to have a modern cross-Win/Mac/Unix office software package (and emacs doesn't count).
I'm looking forward to see what atrocities they try to implement in X11 just to get suchandsuch widget performing in exactly the way they want.
Kevin Fox
Wine and Office (Score:3)
If wine becomes 100% effective for Office, then there may ben no real reason to hold out for a port, which probably won't occur anytime in the near future anyways.
BTW, this was tested with office 97, not 2k. I haven't tried it with 2k yet.
-Restil
An entry point to Windows? I doubt it. (Score:5)
If this report is true, then I think this strategy could really backfire on Microsoft. It's more likely that people will use this as an exit point from Windows to Linux. After all, there's probably quite a few potential Linux users who would switch in a heartbeat, but hesitate because the Office suite on Windows is more productive and more polished. Now, with the option of running Word, Excel, or Outlook on Linux, that objection goes away. (And that's my honest opinion, really: their Office suite is probably the best one out there, but the Windows operating system has plenty of architectural flaws.)
At least it looks like they're operating and planning as two separate companies now. Maybe they think they're going to lose the DOJ case.
Actual quote from my friend when he heard this: (Score:3)
--
This is smart (Score:5)
If it's true, this is a very smart move on Microsoft's part. They've left Linux to its own devices for some time now, and the lack of an office suite has been one of the biggest shortcomings of linux as an office desktop.
But now that viable linux Office suites are coming into their own, and the lack of one won't hold linux back much longer, they can jump in with MSFT Office and claim a big marketshare of office suite installations on Linux.
Hell, if they port DCOM and a bunch of apps that use it, then they can run with the 'it works better on Windows' strategy that they have used with Apple.
Plus, when you've got a few billion in cash, it's not a bad idea to have a few products in your back pocket waiting for hte right time to release.
SteveSo, is WINE porting Microsoft apps to Linux too? (Score:3)
Are you sure their job is to port MS apps? The way I read it, they're basically re-developing WINE, only with non-disclosure agreements... not specifically porting Office/IE/etc.
Wow, that would seem to be WINE's goal as well.
Anyone else read this interpretation?
At this very moment... (Score:4)
At this very moment, a SkiDoo dealer is packing up for his new position as VP of Marketing to Hell.
At this very moment, pigs are growing wings.
At this very moment... Ah, who cares. I don't want that damned paperclip on my Linux box.
Unlikely, here's why (Score:5)
MS doesn't want what little there is of a Linux desktop market share.
Sure, Linux kicks ass on the server side. But aside from loving geeks who devote all their CPU and HD space to Linux, do you know a lot of people who actually think, 'Well, I'd get Windows, but Linux is so much *better* for desktop applications'?
Well, do you?
Linux is still catching up on Windows on the GUI and desktop side. Just look at the Holy Grail of Linux-related GUIs: 'We'll make it as nice-looking as MS'. As long as Linux is running after MS and Windows, they'll never be a threat.
Seriously, who would MS try to convince, here? If people are using Linux as a desktop, then there's something else aside from convenience and wide-ranging applications that they're interested in. Stability? Perhaps. But everybody else still figures stability is a small price to pay for prettiness, especially if autosave is on.
Sorry. MS isn't porting anything to Linux because, let's face it, on the desktop side it's so little of a threat it's laughable.
Freeze the market (Score:5)
This is clearly a response to the Gnome Foundation announcements. The future of non-Microsoft desktops suddenly got a whole lot brighter this week. Microsoft must do everything it can to steer people away from this up-and-coming technology. If they can get people to say to themselves "I'll just wait for MS Office to arrive before I try Linux" then they've succeeded.
Still, even if it's true, I can't see how it'd be very good if they're using MainWin (basically the equivalent of WineLib) to do the port. While the entire Gnome Foundation initiative is centering around CORBA and the Bonobo framework, a ported MS Office will still be using a ported DCOM. Furthermore, it'll look and feel like a Windows app, right around the same time that Linux apps are starting to take on a more unified look and feel. It'll only talk to itself. In other words, MS Office will feel as isolationist and foreign in the future standardized Gnome desktop as the current version of StarOffice feels in the current Linux desktop. Who wants that? More importantly, who wants that and at a cost of $500?
--
More proof of M$ Monopolism. (Score:3)
Well, I love the admission that the article makes. I mean, my last time programming was assembly language on an Amiga 1000. But even with my woefully outdated programming skills, it's painfully obvious that M$ apps have had an interface to the OS advantage over everyone else.
Why should Windows source code be required to port Office (let alone write it)? Corel certainly didn't get Windows source code to write WordPerfect 8.
But the process is even more complex than it sounds, since most Microsoft applications--especially those in the Office suite--use a number of proprietary interfaces, and each application requires specific workarounds.
Mainsoft has access to the Windows NT 4.0 and Windows 2000 source code, a necessity for the work it is doing.
(If M$ wasn't using their market dominance unfairly, wouldn't porting Office require only Office source code, not Windows source code?)
If this article is true, it's just a far more blatant piece of proof that Microsoft is corrupt, and really has to be broken into an OS division, distinct and different from their internet and applications businesses.
Re:Source? (Score:5)
-B
Oooo. (Score:5)
For those who don't recognise that reference- first of all, furrfu- second of all, this is the real leverage that comes with having Office on a platform. Given the expectation that 'oh, Office is on platform X, therefore legitimising it', Microsoft can and does use this as a weapon. For example, they literally told Apple to kill off Quicktime or they'd kill Office for MacOS- the quote comes from an exchange like 'We think it would be better if Quicktime, uh, wasn't.' 'Let's get this straight, are you asking us to knife Quicktime for you- to knife our baby?' 'Yes, we're talking about knifing the baby'.
Should MS apps be established on Linux it'd be like that only instead of dealing with a single point of development and control, MS would be dealing with little groups and individuals, threatening them that if they didn't stop work on their projects, MS would kill Office for Linux (and presumably blame said developer). This degree of blackmail might not work on RMS types but there is a level where it is frightening. Basically it's a sort of extortion, and the point is to engender a climate of fear and obedience. Some of us (mac people into development) have been able to watch this sort of thing going on in the real world for longer than you linux people have... and yes it seems to be illegal, the antitrust case nailed them for JUST this sort of behavior. Now we've got to see if that sticks, or if they get to ignore that as well.
At any rate- there is no benefit from having Office available for your platform. None. There's no significant compatibility between versions, ports are never in synch, it takes large amounts of motivation for them to produce software even half good (i.e. IE for mac) and even if they do they take pains to use it to cut off your other options and change the 'territory' right out from under you so your choices are dead.
The people screaming 'nooooo!' are, ironically, a lot closer to the mark than the people screaming 'yay' here. You've got to look at the business practices that inevitably go along with this sort of 'beachhead'. These guys kill markets- that is their whole schtick. Why would you want them coming over and killing your market too, even if your market is largely mindshare instead of commercial? All it will do is kill your choices without giving you the supposed benefits you think you'd be getting. And that's because, as was repeatedly found by the judge in the antitrust case, they really make a special EFFORT to kill your choices and kill your market- we're not talking about 'network effects', we're talking 'knife the baby'. An MS guy actually accepted those words, mid-negotiation, as descriptive of what they were trying to do. How can that be right? How can that be a market?
Re:Easy because MS will just require root privs. (Score:3)
Most software has to be installed as root, especially if it's going to be of any use to its participents.
Where did you get this idea? Virtually all software I have used in unix-like systems can be installed in home directories just fine. If it's autoconf/automaked, then ./configure --prefix=/home/user. RPM also provides relocation, and I assume Debian has a way, too.
With a file disk quota of 5 megs standard on most machines, do you think most users will be able to install Office (or StarOffice, or anything for that matter?)
5 meg standard? We're talking desktop systems here. If an entire organisation is using it, then individual users won't have to install it themselves. Home users probably won't be using quotas.
What I think the OP was trying to say was that it would require root privs to run, i.e. it would have to be installed suid root. Isn't this the case with their Frontpage extentions for unix? There is absolutely no need for either to be suid root, assuming good design. However, MS aren't exactly consistent when it comes to good design :)
MS Thought Process (Score:4)
Imagine This. (Score:3)
MS makes a Linux distro. They make a closed-source, propriotary DE that supports most of the Win32 API. They include support for DirectX, COM, and OLE. Now, all these changes require major changes to the kernel. While these changes are GPL'ed, MS has now effectivly forked the kernel.
People start writing apps for this new MS/Linux. Because these apps rely on the modified kernel, and propriotary DE, they will not run on regular Linux.
Everybody switches to this new distro, because it has more apps and better technology.
MS has won, despite the GPL.
Stuff to Watch Out For (Score:3)
The conspiracy-theorist in me believes Micros~1 is trying to steal thunder from LinuxWorld Expo without actually making the announcement themselves. However, such a move doesn't surprise me. Bill Gates has never demonstrated loyalty to anything other than making a buck. If he thinks he can make money selling Office to Linux users, he'll do it without the slightest hesitation.
Those who remember the port of IE to Solaris, however, know that Micros~1 will not adapt their apps to the host OS, but will instead try to graft on enough of Windoze's "architecture" to make it work, just barely.
For example, it wouldn't surprise me in the least for LinuxOffice to require a Windoze-style registry, needed to support per-user preferences. This despite the fact that .*rc files have been around forever. Also, expect a butt-load of COM/DCOM components to get installed requiring root privileges (though the need for these prvileges will never be adequately explained).
But I suspect the biggest delays will come from trying to implement Micros~1's demands for copy protection and to prevent "unauthorized" use of "their" software. So, assuming they work out how to translate NT's methods of "license" administration, expect to be required to install a "license" manager that's completely incompatible with any other "license" managers you may have (and may even interact badly with them). Oh, and the CD key will have 96 digits :-).
In short, this is FUD of the highest order, even higher than normal, since it doesn't come directly from Micros~1, thereby giving them plausible deniability. Even if it's true, I wouldn't expect anything to ship for at least a year and, like the initial release of all Micros~1 products, will probably work quite poorly. Thus, even if you're working on an office suite, this story may effectively be ignored.
Schwab
Finally!!!! (Score:5)
Re:A good idea but... (Score:3)
NT itself is stable
If NT itself allows applications, after they have crashed, to leave leaked memory or leve the system in a strange state or leave the system in a slowed state then it is not a stable OS. It may not fall/crash but it is not stable. Kinda like a ship in a storm, your footing is not stable but, hopefully, the ship won't sink. You may be flung overboard but, hopefully, the ship won't sink!
From the makers of IE for Unix... (Score:3)
So from what I can gather, these are the geniuses that brought us Unix IE. Yup. Just look at the explosion of IE users on Unix. If they do just as good a job on Office, then MS better watch out or their OS market will disappear overnight!
My favourite part is how they say their software isn't a Windows emulator. They just build every single DLL that you'll ever need into a Unix library. And probably a registry too, for good measure.
And you thought administrating Windows was bad enough on a Windows box...
--
Re:A good idea but... (Score:4)
Re:interesting? (Score:5)
Weather report (Score:4)
Re:Hubris (Score:3)
What the hell? (Score:5)
Porting DCOM to UNIX is one thing, but Office is another beast entirely. Microsoft nearly destroyed their market for Mac applications when they tried to offer a weak port of the Windows version of Office -- people simply started refusing to upgrade. These days, the two have pretty much completely different code -- you can't really port the Windows version of Office to any other OS, because they're joined at the hip with DLL-Hell, private system calls, etc.
Re:A bridge to Windows? (was Re:Hmmm) (Score:3)
I think (one of) the other thing(s) M$ is trying to accomplish with this move is to shore up the lifespan of their proprietary data formats. The targets are coorporations who have licensed Office. One of the main things that seems to slow the move off of Windoze at a corporate level is the tremendous investment in M$ Office and legacy data that is already in the Office formats.
The Office data formats are, after all, the key to keeping their current captive customer base captive. The office applications themselves simply aren't good enough on their own to do that. A *nix Office suite is a way to keep those formats alive, which is important to M$, since if the formats are dropped in favor or, say, an open standard, then there is really no incentive for corporate customers to stay with M$.
M$, I believe, fears that as work goes forward to make format conversions easier, it will be more cost effective for a corp to invest in data conversion and move off of the Windoze platform than it will be to keep putting up with (paying for) the spew of M$ corp.
Other office suite software vendors are targetting the office data formats and application functionality. If one of those outfits gets there (usable in a corp environment) first, M$ would be left with their collective asses uncovered. So, for M$ to produce a Linux Office suite is also a CYA strategy...
Heh. Disingenuous is M$'s middle name. Their contempt for users -- and everybody else, for that matter -- is huge. They really, really don't expect anyone to figure it out, and when someone does, they apply spin. I don't think you misunderstand.Also, note that this effort is going to be incorporated into the spin machine. 'See, we develop apps for Linux, too!' It's a good PR move for M$, since they will co-opt a certain percentage of *nix advocates with this move. Since Linux advocates in particular seem to be the most vocal and persuasive of the M$ detractors (often because they are former M$ users, I think), anything M$ can do to cut down on their number is a plus.
All in all, it's about Leverage.
Usual attack, beware (Score:5)
Then of course they don't do it and everybody thinks there must be a problem with the JavaStations (which there was the OS sucked).
Now they are going to try and do the same thing with Linux... tell everyone... we are porting to Linux when they are Scared of linux because linux is going to eat the mid server market of win2000.
Then they will come out saying "It doesn't work" and spread FUD around it. I hope star office is as good as they claim, and I know MS can't diss the os like they dissed the javastation.
marc
If it is anything like IE for Solaris... (Score:5)
The marketshare is just too big (Score:3)
Ok, so they port applications to *x. It's just a business strategy. It's a new market space for them to grow into
And the bottom line, for the current CEO, is that if it pays off, the stock holders will be happy. Also, it'll probably help their anti-trust appeal because they'll be able to show that they're not only in the business of OSs, but also in providing valuable applications to the entire user community.
Just imagine the Office Assistant... (Score:3)
"Did you know: You can get all your office work done faster, with more multimedia excitement and internet connectivity with the new Windows Milennium Edition! Order today!"
"Tip of the Day: In order to enable the remaining 95% of functionality, click here to install Windows over /dev/hda1! Windows Milennium Edition works hard and plays hard!"
If It Was On The Internet, It MUST Be True! (Score:5)
Porting an installable, standalone MSOffice to Linux doesn't help them get there so I would suggest you're crazy if you think this will ever see the light of day.
Now, they may VERY well be porting some sort of ".net client" stuff to Linux. I'd expect that.
Info on how they'll do the port, and why (Score:5)
For those that don't know (you certainly wouldn't from the article), Mainsoft produces a toolkit (MainWin) which implements the WinNT/2k kernel and MFC on various flavours of *NIX, including Solaris and Linux. This enables one to take a Win32/MFC program that was developed on windows and (in theory) have it work on *NIX just by linking to their MainWin libraries. The toolkit has been discussed some here on
I/we use the toolkit here at work (a MAJOR hardware company) to port our dev tools to *NIX, and we've had quite a positive experience with it. Sure there are problems here and there, but for the most part they're due to our windoze developers making assumptions based on the program being run in a win32 environment (things like endianess issues, or the fact that windows uses backslashes for dir separators rather than slashes). It has enabled us to port a product consisting of over 300,000 lines of code without having to rewrite the whole thing. I don't imagine Mainsoft would be having as hard a time porting Office as people are making out, not only because the toolkit is good IMHO, but because in my dealings with them they have seemed like a very sharp bunch of people.
"Now," you say, "why would Microsoft want to port Office to Linux? Isn't Linux their enemy?"
1) Further entrenching the
2) Doing this port will lend MUCH credibility in the public eye to MainWin. If they are lucky, then people will start organizing their multi-platform development strategies around it right from the get-go, and thus Microsoft will "lock them into" using the MFC development model. Right now people tend to use Mainwin to port apps they already have on Windows to *NIX... perhaps if MainWin got enough prestige people would decide right from the start that if they are doing a cross-platform app that they will do it in MFC and use MainWin to do the porting.
Do NOT underestimate this... Mainsoft (and through them, Microsoft) makes some serious bucks off of licensing/royalties for products that use MainWin, as their code is actually linked into yours. If you just make your app on windows and compile with Dev Studio, you pay no royalties, but with a MainWin ported app you are shipping with compiled libs that implement MFC and the NT kernel... that means $$ for Mainsoft and Microsoft.
It especially means $$ if people start deciding that they would like to forge off into the Linux arena because using MainWin is so much more attractive than doing a native port from the ground up. Companies that before were never even considering doing ports to *NIX might start thinking about it if this MSOffice port goes off well because they will say to themselves "shit, we hardly have to do anything ourselves to do this," even though that's not quite necessarily true.
This is very good for Linux in a way too... it means that you will be able to get much more of your favourite apps on your favourite OS.
Mechanik
Hmmm (Score:5)
It's a pitty it also works the other way around, use an Office for Linux as a Bridge from Windows. There is no one way sign on this bridge!
Official PR Release says UNIX -- not Linux (Score:5)
here [yahoo.com]
MSFT has an established business porting its applications to Solaris and HP/UX. This does not mean they will port to Linux.
Now hiring experienced client- & server-side developers
Why no Server Apps? (Score:4)
<p>
Well, this started me thinking - I use Linux because it's one more step into Unix; I've been using GNU and Cygnus utils long before Linux was around. I just like the paradigm.<p>
But I also REALLY like Word for Windows. WfW 97 is my favorite, and I can whip out a document in less time than it takes most people to read it. All the keycombos are hard coded into my fingertips, and I have dozens of style sheets and macros that eat perl and/or PHP-generated data.<p>
As an administrator, I loved Exchange+Outlook. My users dug it, building custom objects that they'd mail out, stuff like that. And of course, you need Excel and Word to really get the power of Outlook.
<p>
But Linux -- now Linux I've had running as a server (before that, AIX or Solaris). I like the desktop, but miss Word. And I don't see anything like Outlook+Exchange out there, which of course requires...
<P>
WAIT A SECOND!!! Why are they porting desktop Apps? Why not Linux Apps? Linux has a greater marketshare in the server arena, anyway, and Exchange or IIS for Linux would probably ship more units at a greater profit than Office.
<p>
Unless... they don't consider the Linux desktop viable, and just want to make a show to the DOJ (of course, you have to run WinNT BackOffice to support the software on those Linux desktop boxes).
<p>
Very interesting... Office is less useful without BackOffice, and BackOffice needs NT. Office keeps people in MS, and then once they go above just a few users in an office, they start racking up reasons to move to Windows. *Especially* if Microsoft.NET turns out to be way watered down (like most MS final releases) and is just a tighter, nicer BackOffice.
<p>
No, I'm not paranoid, and I'm just happy that I can sed in a bash shell, not pro-Linux or pro-Microsoft, but IF a decision like this has been made at MS, it's after MUCH discussion, and both server and desktop apps were discussed, and you know DAMN well that MS thought long and hard about the long and short term consequences of every action.
<p>
--<br>
Evan
This doesn't mean we'll ever see it (Score:3)
Porting office to Linux is a huge project, and Microsoft has to be prepared for the contigency that Linux *does* take off in a market that Office addresses - if not the desktop, then perhaps in some embedded/appliance apps (imagine a dedicated Office appliance a la word processors).
Given the lead time on such a project, they don't want to have to wait a couple of years if they decide to exploit such a market - so they have to do the dev work now.
This doesn't mean anything other than Microsoft is hedging its bets.
A Port Does Not Mean Boxed Sets at CompUSA... (Score:3)
"Microsoft Israel" (where they put together their clone of IBM's MQSeries, which is a pretty successful product) may be doing "a port," but that is a far cry from Putting Boxes On Store Shelves.
It may be that Microsoft is leaking this stuff so as to diminish peoples' committments to the "more nearly native" alternatives of StarOffice, ApplixWare, WordPerfect, and such.
People that decide to wait for whatever Microsoft might release are obviously not buying what the other guys have today. This is how IBM marketed the IBM 360 back in the 1960s, to the great detriment of many other computer manufacturers.
IBM finally did release OS 360 and related hardware, albeit late, expensive, bloated, and buggy.
The parallels should be obvious :-).
Furthermore, the DCOM comments really are important; "modern" MS-Office software depends heavily on COM and COM+ components, which means that the first step to getting MS Office running on Linux would indeed be the port of COM/DCOM/COM+.
And we don't know if this "announcement" represents a product that will actually become available, or whether it is a "vaprous" experiment, intended to use Fear, Uncertainty, and Doubt to discourage sales of the competing products...
Source? (Score:5)
Good for Linux OS/ Bad for Linux Apps (Score:3)
Like no-one is going to pirate these apps, and I bet MS wouldn't care untill they have the market, and then they bring the hammer down. (Rings true of netscape, does it not?)
This is news, that's for sure. We are still to find out if it's good or bad.
You know hell has always been frozen, right? (Score:5)
In Dante Alegheri's (sp?) Inferno, the center four regions of hell -- reserved for the worst kind of sinners -- are made up of a gigantic frozen ice plain.
The sinners are frozen into the ice, completely unable to move or respond to external stimuli...
Good (Score:3)
Anyway, all I want is IE5 (doesn't even need to be 5.5 -- 5.01 is fine) for Linux.
As a web application developer using HTML/CSS/XHTML/ECMAScript/XML/XSLT/XSD I cannot make it without IE5.01+. (Yes, I grab the nightly builds of Mozilla but remain unmoved).
IE 5 for Linux!
Now hiring experienced client- & server-side developers
If you can't beat 'em (Score:5)
Seriously though, it might not be too bad. For instance, the corporation I work for's e-mail standard is Outlook/Exchange which I'd like to be able to run on Linux (my primary desktop). I haven't found a suitable Outlook clone yet so I can get my mail easily. Incidentally, I tried the fetchmail thing, they don't have NTLM enabled and won't turn it on.
Not to mention how many times I've recieved e-mail documents containg Word or Powerpoint presentations that StarOffice couldn't convert very nicely.
I don't know about it being a bridge over to Windows, however, some good could come out of it. You'd think they would start by helping out the wine project, but then again, thats not M$'s style. They'll probably take the wine code and make it proprietary.
Re:Imagine This. (Score:3)
A proprietary desktop needn't be integrated with the kernel to be dependant on a specific version. If MS retools the kernel, and the desktop is an independant entity, but requires those changes, then MS has essentially tied the non-free desktop and the free kernel together. Think of it like Aqua. The changes that Apple made to FreeBSD aren't really significant in itself, but simply enable stuff higher up in Quartz and Cocoa. If MS had done the same thing, except with Linux, then effectivly they would have gained control of the OS without violating the GPL.
As for desktop antogonism, that's not possible. If you're going to write an application that supports all the features of a DE, it is nearly impossible to be destkop antagonistic without a whole lot of problems. If MS bases it's desktop on Win32 and Win32 only, a developer would be force to choose between that, and programming for GNOME or KDE.
I never said MS has won. In the case that this hypothetical scenario happens, it will have won. And if you look at it pragmatically, Linux winning DOES require MS losing. By definition there is one winner. In terms of OSs, there is only one winner. Windows beat OS/2. NT largely supplanted Netware and UNIX. There has to be a winner. (Especially in consumer space where the number of apps a particular person needs is greater and much more diverse than in say server space.)
Never assume M$ has just one motive (Score:3)
- The Hedge Hypothesis: If M$ is forced to split into M$Windows and M$Apps, this gives the "apps" part of the company a leg up in breaking into a new market.
- The Appeals Hypothesis: Office for Linux could give M$ a new argument to use in the Appeals Court or the Supreme Court: "see, we make Office for these other two operating systems, and we sell decent amounts of them, so we're not really a monopoly." Mac Office alone might not cut it, but Mac Office combined with Linux Office may tip the scales.
- The Standard M$ Hypothesis: Shut down StarOffice, WordPerfect Office, the Gnome Foundation and their backers, etc...what do you bet that M$ gives out a "crippleware" version of Linux Office free?
- The Poison-The-Well Hypothesis: Once you get Linux users (maybe recently switched from Windows) to embrace Office, use this as a lever to move them (back) to Windows. How? Proprietary file formats, faster upgrades available for Windows, etc., etc.
- The FUD-Factor Hypothesis: If Linux Office turns out to be buggy, slow, etc., M$ can turn around and tell developers, "see? Linux really is hard to develop for, you should really develop for Windows instead."
- The If-You-Can't-Beat-'Em-Join-'Em Hypothesis: This is actually a stepping stone towards a Microsoft Linux distro, which will be a replacement for one or more existing M$ operating systems. (Farfetched, I know, but...)
I'm sure you can think of other possibilities.Eric
--
AV industry says: YES! (Score:5)
And in the anti-virus industry, there was MUCH rejoicing...
- Tim
Re:Hmmm (Score:3)
Sure there is: down. Surely I'm not the only one who can't shake a mental image of the Tacoma Narrows bridge [bris.ac.uk].
Re:Easy because MS will just require root privs. (Score:3)
I'll bet you almost anything that a MS installation would chmod 06711 most of the files and make sure root is the owner.
Buggy code will take down your system and corrupt the fs on the way.
Will you people wake up? (Score:5)
Do you really think this isn't a direct response to the "GNOME foundation" [slashdot.org] announcement? I mean, come on people!
----------
There Is A User Born Every Minute (Score:3)
The article says they are having a rough time of it, even with the Windows source code. Maybe the strategy will be to flood the market with poorly written Linux applications. People will say stuff like "Office runs bad on Linux, Linux sucks".
I have to admire Bill Gates as the PT Barnum of computing. He intends to use Linux as a gateway to get people interested in Windows. Maybe his Linux desktop will have a link on it that says "This Way To The Egress".
Sure Linux is stable, sure it's free and all that junk. But where's the *showmanship*?
Re:Oooo. (Score:3)
The correct answer to this is "KYOFB"; "Knife your own baby."
I think that most "little groups and individuals" would probably pay money to get Microsoft to kill Office for Linux. Threatening to kill Office for Linux isn't much of a threat. I know that if Microsoft came to me with that sort of threat, I'd laugh in their face and tell them to go ahead and kill Office. Would you do otherwise?
Some of us (mac people into development) have been able to watch this sort of thing going on in the real world for longer than you linux people have...
This says a lot about how "independent" Apple is
But Linux isn't going to Microsoft on hands and knees pleading, "Save our sorry asses by porting Office to our failing operating system", like Apple did. If anything, Microsoft is attempting to muscle in on Linux turf. Entirely different situations. Entirely different outcomes.
Fits with the Justice Department Split (Score:3)
The Applications company will want to have access to *all* markets. They see the writing on the wall with all the new and improved desktop initiatives in the Unix world, and figure that there is going to be some erosion of market share for the Windows desktop.
They probably are also trageting us geeks who have to do a lot of document shuffling for work. We'll be able to have our cake, and read Word documents too. They figure IS managers will say "Hey, it's guaranteed to be compatible, since it's Office."
Still, it'll be hard to compete with free. Star Office is pretty good!
-
bukra fil mish mish
-
Monitor the Web, or Track your site!
Why this makes sense: (Score:4)
This makes sense, it really does. Look at the following, and I think you'll see where I am coming from.
1. PR. The whole monopoly thing is starting to get to them. They face formal scrutiny in the US, Europe and India. If they do this, they can look and say "but we really do have competition". "We did a port at X number of millions of dollars to take advantage of this competitive market".
2. They are a business, something that a lot of people seem to forget. If they can make money on this up and coming OS (now that it is starting to break out of geekdom), why not? People seem to forget that they also make Office (and other products) for the Mac.
3. StarOffice. People use and buy Office (which is far more profitable for them than their OS's), because it is the defacto standard. Aside from a few die-hard types, it is accepted worldwide (except for China - different standard). StarOffice is being given away for free, and MS doesn't want people to get in the "habit" of using something else. Remember they considered Sun's intro into the browser market seriously enough to spend half a billion dollars (US DOJ figure) to combat it.
4. They need to show the world that they can play nice. MS settled the lawsuit with Mac based on a cash investment (non voting stock) and a willingness to make MS Office 98. Without MS Office 98 (pre iMac), it is was widely considered that Apple would have gone belly up. MS had more to risk by Apple going belly up than Apple did. Take Apple out of the picture at that time, and their would be no perceivable possible competition (Linux was not nearly as popular than, keep in mind.)
5. Market penetration. There are *nix shops that don't use MS. Once you port to Linux, it isn't that great of a leap to port to *nix. MS wants these markets, and this is a way to gain a foothold there. Regardless of what you think about the company, this would sell like crazy.
6. Microsoft.Net. This is another way to sell monthly licenses. Once people start to see some of the "features" that work with Office, they will want access to the rest of the features. It's the "collection" syndrome, people can't stand to know something is available, and they don't have it. Enough users start to demand features that would work with say, MS Exchange 2000, and management just might listen.
7. They are losing some customers to Linux. A lot of these people despise the MS OS's, but like the office suite. If they can see a familiar face in their new unfamiliar OS, many people would jump at the chance. I think that a significant number of the people who are former windows users would say that office is the 1 thing they miss most.
8. If they are building MSLinux (which they certainly could), this would be a way to get people to switch to "their" flavor of Linux. Make the desktop similiar to Windows, maintain the "look and feel" that someone who has used Windows knows, and they could easily become bigger than Redhat. They maintain their standards and control, and the masses would flock. Before you bash this statement, look at the first fundamental rule of marketing. Brand recognition is what counts. It is well established that the masses will flock to a brand that they know. Remember this would not be ported for the geeks that use Linux, this would be ported for the masses.
This is obvious (Score:4)
Then, start to make it suck and fall well behind the Windows version, forcing more and more users to switch over as they lose support. Finally, discontinue it altogether, leaving Linux users with nothing at all (when now they have alternatives), and crush all possibility of Linux reaching the desktop any time soon.
For that matter, I'm truly surprised that there's no MS Linux distribution, which they would push and market heavily until Red Hat, Corel, and others went out of business, all other distros were ignored, and they were the only game in town (or at least had gathered like 97%+ of the market share). Then, again, just dump the damn thing. Kill it off, and leave everyone sucking wind. While it may not kill Linux off altogether, it would set the effort back a decade or so, and give MS Winblows the opportunity to actually grow into a stable OS that works sometimes, and cement an even greater share of the market.
Re:If it is anything like IE for Solaris... (Score:4)
I hobbled through the shared libraries and whatnot one day.
Know what I found?
Most of Windows! YEP! References to CONFIG.SYS, AUTOEXEC.BAT, instructions for how to configure Plug and Play devices, PCMCIA devices, a SYSTEM.INI, etc, ad nauseum.
No wonder a Windows port isn't far behind -- the Solaris/HP ie/oe "port" isn't much of a port. It looks like they just sort of sandwiched enough shit into Solaris to give enough of a Windows-like environment to make their pathetic applications execute.
Further evidence?
They don't use X! Well, they use it, but they use the lowest level native (widgetless) output. No font server, no nothin'. It CRAWLS over a 1 megabit connection, and is barely useable of a 10 megabit connection. They render the freakin' fonts one bit at a time!
HELLLOOOOOOO??!!! Microsoft! It's an operating system + Xserver, not HARDWARE! CHRIST! Do you have any unix-literate software engineers? As near as I can tell you've hired some "consultants" and a bunch of VB-mouse-click-wizard-totin' hacks!
--