Microsoft Renovates Office Suite as a Web Service
foobsr writes "According to an article in EcommerceTimes, Microsoft is trying to migrate Office from a product to an online service with a focus on automating collaborative work. Quote: 'Making collaboration faster, easier and more efficient will be the next revolution in worker productivity, and we want to be in the forefront,' said Peter Rinearson, vice president for new business development in Microsoft's information worker group"."
Many programs need to work on operating in a collaborative environment. If you've ever coded in such a setup you can really understand how this will be a good thing for office software.
--
WHO ATE MY BREAKFAST PANTS?
But for Microsoft, which is starting to see its growth slow, reinventing that suite of old reliables including Word, Excel and PowerPoint has become nothing less than a key to its future.
Umm.... Yeah. I remember when MS finally decided to get on the Internet bandwagon, and started putting "Internet functionality" in every single one of their applications. Remember how poorly that was implemented, and how little of value they were actually able to add to the various Office apps?
I don't see this as being much different. Buzzwords, ooh-ahh's from the PHBs, but little increased value for the end user. Collaborative PowerPoints? Um... Ok. Isn't that what source code control systems are for, even for binaries? Pure vaporware, baby. I mean look at this:
The new design makes programs like Word, Excel and Outlook e-mail part of collaborative work spaces. In theory, an employee working in Word could tap into all the corporate information on a customer or project.
What? What the heck does that even mean? Sounds like they're dreaming about some sort of uberlayer on top of all Office apps that will let you somehow get information no matter where it's stored. AND do it collaboratively.
*cough*
Righty-o. Believe it when I see it, chappies.
I think Microsoft is on the right course here. I pass around docs all the time and use the ever problematic "track changes in word". A wikipedia style approach would be nice, as long as it's usuable and handles images well.
I hope they don't mean a web service as in a C#/ASP.NET web service. I played around with those some. They are very fast and easy to work with, but not half as responsive as a native application. I've always liked plain old simple programs, and hope MS changes there mind if it is anything like what I've used (I'm probably wrong and it isn't, didn't RTFA).
Help Fight SPAM today!
Pretty soon, Office will look like Lotus Notes.
Oh joy.
---- The above post was generated by the Turing Institute. Maybe.
I'm sure they will Call this INOVATION when we all know its just the same old stuff with a web brower on it.
How lame of Microsoft.
So now you don't have to worry about skript kiddies making your computer go "beep beep" and deleting like HALF of your report.
Now it will be deleted every 5 minutes and the save-as function won't work. But that's a feature.
Inovation!
Not a Twitter sockpuppet... but I wish I was.
And we want you to give Microsoft a copy of all of your important business documents. Who could think that was not a good idea?
I'm an American. I love this country and the freedoms that we used to have.
I seem to recall there are already web-based office suites available - Hyperoffice comes to mind as one...
Oh great, the two biggest nightmares that exist in the Slashdot crowd are about to combine: Clippy and ActiveX.
AAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHH!
It would be cool if it didn't suck.
...since according to the article:
"Because the next version of Windows, called Longhorn, may not ship until 2007, analysts say, the Office overhaul is needed in the meantime to deliver more Web services technology to the desktop. The new capabilities in the Office system are also needed to lure software developers to create more applications that run on Microsoft products."
If they can't reinvent Office, and their next version of Windows won't be out until 2007, their income streams will dry up and they'll need to tap into their cash reserves, which I'm sure is the last thing they want to do.
Find out about the Lexus Rx400h Hybrid!
I think this is a reasonable goal, but like mankind Microsoft shouldn't evolve too quickly. Office still has its share of problems and I would really dread the day when my boss says lets put all of our work and research online. The net and any online collaboration programs are way too risky for my taste.
Making collaboration faster, easier and more efficient will be the next revolution in worker productivity
...And they should get rid of that fucking talking paperclip while they're at it.
Aren't they kind of putting the wagon before the horse? Shouldn't they work on making the product just work correctly when you're by yourself?
Trying to work in Microsoft Word is like trying to build a house of cards during a fucking earthquake.
The theory of relativity doesn't work right in Arkansas.
What are the odds that these applications will run on something besides IE? Is this the real reason Microsoft was talking about making a new version of Internet Explorer?
Or am I completely misinterpreting what they mean by Web services?
Microsoft will either perpetuate their poor programming practices to a platform that will allow viruses to become even more virulent and worms to spread even faster. Wonderful. Or they'll take this opportunity to build apps that will run cross platform. Alot of potential good here. Mixed with alot of potential bad. Increasing the need for the Windows Server platform if they don't create Office as a cross-platform collaborative environment. Will be interesting to see how this one plays out.
Scientia et Potentia
Since people would probably stop buying newer versions of Office because they won't offer much productivity increase, I think this is a way to force people to keep paying money for Office.
As quite a few people have started realising, the web is the platform of the future. There will always be room for locally run 3d graphics apps/games, but the web just makes sense for business apps.
Joel on Software has a good article here.
Since the win32 API is meaning less and less, now is open sources chance to win the API wars :) I'd love to see a mozilla based explorer.exe replacement. Easily customised, easy to lock down for sysadmins, open source, cross platform. It would make migrating from windows to linux be painless, as the interface would be the same. You could transition incrementally. If you still need office, run windows for a while with the replacement shell. Then, as people get comfortable with the new environment, move them to wine or open office.
I can think of heaps of reasons to switch to a shell i've got full control of. Security being a major one. XUL apps too; you could quickly whip up an app in XUL + javascript which would do all your database transactions. What companies don't have a database of some sort?
How many times have Microsoft internet based services been down for extended periods? How many billions would such an outage cost, in worker productivity, if office was provided a a web service? The implications are downright scary.
"To those who are overly cautious, everything is impossible. "
This is not new. I was at a conference over two years ago and heard a talk about .net from some MS developer. Every other word out of his mouth was "software as a service".
What I took home from this was the notion that MS wanted to migrate everything they do to web services... why?
They claim it's because all updates will happen automatically and be transparant to the user.
My theory is that it's really because it gives them total control over what you can do. You will never own anything. Just rent the service. You will always be trapped in the "pay your MS tax or you can't even open your own documents" nightmare. What a terrible plan for the users.
Microsoft needs to realise that Office is firmly fixed in the minds of 99 percent of its user base as an word processor/spreadsheet/presentation graphics/database/email client suite. It wouldn't matter if they bolted a space shuttle onto it, as far as the overwhelming majority of people would be concerned, it would still be all about Word, Excel, PowerPoint, Access and Outlook.
Trying to leverage Office into other roles is not going to work. Yes, some people will make use of a web service feature but it will go virtually ignored by all but that tiny fraction that tries out everything new Office paradigm because Microsoft tells them that it's the best thing since sliced bread.
Office users get what they want out of Office right now. They're happy sharing documents by email and other means. So why would they and their organisations throw all that away and take the time, effort and money to implement a web services-orientated approach? Who wants to explain to the CEO that he's got to stop asking people to email him documents and start asking them to publish them, and that he's got to do the same with his own output too? Who wants to retrain all their end-users to this new way of thinking?
Microsoft has a real problem right now with its Office suite and it knows it. It's not that Office doesn't work, it's that it works too damn well: what virtually every Office user wants to do document-wise has been possible for quite some time now.
There's very little that Microsoft can do to the individual applications to improve them by delivering new features with tangible benefits, and certainly the applications in Office XP weren't significantly better than those in Office 2000, so it's obsessed with "improving" Office by trying to manage how people work. This kind of improvement might deliver results in Microsoft's labs but in the real world, where people are resistant to change and have a "if it ain't broke, don't fix it" attitude, it's doomed to failure.
"Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
subscription based services. This is a step in that direction. Microsoft is scrambling for a way to get people to 'subscribe' to office because they ran out of features worth upgrading for with office 97 (well, for probably 80% of thier users anyway, and that 20% isn't gonna sustain the growth shareholders have come to expect).
:).
I don't see the benefit to this for anyone but Microsoft. I don't think the Internet could handle 250 million people 'streaming' office. Which means something's gonna get installed, and it's gonna be just as much a pain to fix when it breaks as the current office. Oh well, maybe crap like this will encourage openoffice.
Off topic, but I've notice a funny trend in office suites. I'm seeing more and more people running openoffice because their computer got laid waste by a virus, and they didn't get any CDs from thier OEM (or lost em). Buying office without buying a computer isn't an option for most people, so they're driven to oo.org
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
Also, Bill G. recognizes that the medium itself is but the vessel. What goes in the vessel is the future. MS wants to sell you the server OS that gives MS content (Office and other apps) to a MS desktop, all bundled nicely together with Longhorn and the ability to ship sandboxed code over the 'net.
Let's not forget the reason we all moved to webapps in the first place: single distribution that updates for everyone at once. No more multiple versions and testing on all sorts of configurations. The next version will be the single one they keep on the server, and the configuration will be the IE web browser.
MS Office over the internet will succeed where the Java Web Start failed. Soon to follow will be the anti-virus guys, because it's already here and I'm sure TrendMicro would also like to dump the development costs of a desktop client for an all web one.
This one is a good call by MS.
I remember working on a web version of Wordperfect 10. It was using a tool like Citrix or Webex to deliver the applicaion over the internet from Corel to your desktop. Pretty neat way to try out software IMHO.
I see now that they've dropped in in favor of a stripped down demo download. I'm curious to know why they took it down, as it might be a good reason for Microsoft NOT to run Office as a web service.
Anyone remember this? Anyone know why it went away?
There is no reasonable defense against an idiot with an agenda
:wq
Kinda makes you wonder what reverse engineers, keygen programmers, and software crackers are going to do when they have to pirate a web service instead of a normal app.
Adding a full-blown language with OS hooks into Word, responsible for an entire generation of viruses, wasn't enough, let's make Word even more "powerful".
They seem to keep ignoring that these programs (and whatever they may spawn) have the same privileges as the employee, so if the employee "could tap into all the corporate information" then so can Word and Excel and so will the next macro virus using the new "technology".
Besides not liking to pay for software as a service, there was another huge problem that still is a problem. WAN reliability. I have been amazed at all the people that don't really understand how *unreliable* the wide area connection is.
I had a case where a business was going to ditch their business management system (for an insurance sales co) for a 'web based' system. this was just *after* his dsl had been down for a week. I tried to explain that if he was using the web based system and his dsl went down he would not have *any* information available. And he didn't understand/believe me.
And then their are DOS attacks and other problems on the internet that may prevent you from getting to the MS Office web server.... sheesh.
I expect this to crash and burn again.
eric
I think that's a wonderful move for them really. That's exactly what people have been begging for. It's important that business increases its dependance on the internet as a means of doing business. I think the idea is very sound. By the way, did they ever fix that problem with ActiveX being a huge security risk?
MS Office over the internet will succeed where the Java Web Start failed.
Microsoft has already totally compromised the security of Windows by uintegrating the desktop with the Internet, now you think integrating the office suite with the Internet is a step forward?
A definition of insanity is doing the same thing over again when you know it doesn't work.
You may not realize this? But you hit on another benefit of a web based app. Controlling piracy.
Add in guarenteed revenue stream. Also if MS does this and it succeeds (bad idea or not), then you'll see a rush of other web-based apps.
Throw in the DRM MS has ben working on, and...
Are pirate's days numbered?
... the idea of combining poor security with placing reliance of your business operations on the net in such manner....
Yeah its a real good Idea you have there MS..... keep up the good work...
-----
Help promote Linux, support MS insanity.
Office and SharePoint 2003 have begun this move. It is not turning into a web service as the summary suggests, but instead utilizing web services for collaboration.
The company I work for has been using SharePoint for Issue tracking in our software applications for nearly a year. It was way easier to setup and use than bugzilla and several other free alternatives. And the issue tracker is a very secondary feature of SharePoint!
It allows the creation of document libraries that can associate arbitrary metadata with documents. When you save a document from an Office application is can actually be saved directly to the SharePoint document library (you can browse to the web page in the save as dialog and it shows a little html based page right in the mini-explorer and you can save there like a normal file). After clicking save, if the document library has been extended with metadata (by any non-tech-savvy user) you are prompted to enter that data.
You can also create document workspaces which are document libraries that have an associated message board, contacts list, task list and other odds and ends. All of that information appears in a sidebar in any office application which lets you instant message, email, or assign a task to a contact related to the document you are working on. Documents in any type of document library allow for versioning and check-in/out functionality.
InfoPath is probably the coolest Office application when it comes to collaboration. If you fill out an InfoPath form, the xml output can be funneled into a SharePoint document library which can calculate statistics from the documents and sort/organize them for you.
Its only the first version of the Office System that uses this functionality, and we all know it takes Microsoft 3 tries to get anything just right. Luckily, the system works well on the first try, I can't wait for the third attempt!
http://brandonbloom.name
...But it's already a reality. For example, I have been working on a project for BMW that is just that: a freak hybrid between Powerpoint and CVS. It's implemented in Flash on the client side, and backed up with a Linux machine running Apache, PHP and PostgreSQL.
Images and documents are stored on a central webserver. All administrative interaction is mediated through the flash application. The editing environment is the playback environment. All relevant historical assets and information are immediately available. And, one of the design requirements was that the whole thing needed to run on Macs, so I don't see anything from Microsoft edging it out anytime soon. The project is like a poster child for Joel Spolsky's recent "How Microsoft Lost The API War" article.
This link gets rid of the awful colour.
www.timcoleman.com is a total waste of your time. Never go there.
Many programs need to work on operating in a collaborative environment.
Do you have any idea how very nearly impossibly difficult this sort of thing is? It makes The Theory of Relativity look like a stroll on the beach.
Indeed, the sorts of problems encountered [when concepts like "TRUE" and "FALSE" cease to have meanings independent of their times and places] bear more than a passing resemblance to The Theory of Relativity.
Think I'm kidding? Try reading the RFC for the Network Time Protocol:
All that NTP seeks to do is get two computers to engage in the most fundamental task of computing: Come to some reasonable agreement as to the time. And yet, the RFC requires just about a PhD in mathematics and about 1000 pages of background reading from old AT&T switching standards just to begin to get an idea of what the heck is going on.The first thing to realize is that a web service no longer indicates internet anymore. It's a shift in paradigm. It's time for a lot of you guys to throw out your blue polyester shirts and suspenders. Web simply means it's delivered from a central location and typically works through a browser or derivative of a browser. This doesn't mean 2 billion users will be streaming office from microsoft.com. It doesn't mean that when MS's servers go down that the entire world will be without Office.
.NET reaches full maturity and is available for other platforms. Realistically, Linux might be running MS office in the near future.
This is simply the realization of the thin client paradigm. As corporate environments go, it's about time.
And before anyone panics about all those stand alone machines out there (like us developers are all so fond of), there are a bunch of appies out there that are essentially written this way already. VS.NET is web driven. That front end is all xml/html driven. We see it with the MS management console and MSC snappins for it too. This is the sort of thing we're looking at with the future of office.
The front end will be web based. The back end will likely have a few different options and standalone on the local machine I would wager will still be one of them. But at the same time, the back end could be centralized greatly simplifying mangement. I wouldn't be suprised if the next incarnation of Visual Studio can be set up to compile on a central server.
This should in theory simplify development of the Office software and reduce all versions of Office to a single codebase once
is there an open source project that mimics sharepoint?
i have no use for one whatsoever, but the OSS community has done a bang-up job with open office and exchange clones, so now my curiosity is peaked.
wish i could code. no wait... i'm glad i can't.
scott king
So does this change in Office mean M$'s VBA viruses will now run on their server instead of my workstation?
Was going to moderate this one, but I would just like to say, if there wasnt a windows, odds are there wouldnt be a Linux (just take a good honest look at the gui, the coding behind it non-withstanding). And if there was a linux, all the cute little sypware and bonzi-buddies of the world would have been written for the prodomatly linux world. Its easy to sit back and bash MS, but if they wernt around, it would be someone else. Its just smart to code crap for the prodomant OS, especially if your purpose is malware.
I am that much more enlightened and proportionally disillusioned
Please let a router outage determine whether or not I get any memos written!
I'll be really curious to see how the licensing will be handled. While this model of "services" may be OK for corporate and home use, I wonder how it will go for educational settings.
Currently many of my students have Office on their "home" PCs. They can also use it in the labs, since we have a campus site license.
However, if the software moves to the web and is licensed by campus, will the software's access be limited by (campus) IP address? What happens to the kid that goes home for break and needs to use Word or Excel?
Sure, the campus can add some kind of password system to let the kid access the software via the campus license from home, but now you are adding work to overworked (and underfunded) IT departments.
Yeah, this is going to be interesting to watch.
OK, I'd love to see OpenOffice or some other option take off, but our campus is so bound to Word (hell, I get three line memos in a Word doc attached to an email), I can't see the secretarial force even open to considering a platform change to other software.
Centrally managed, downloadable applets and applications have been built and sold for years. I used to work for two different 3270 companies, and they both had systems that did this, as Web applets, as standalone apps, and as hybrid (split-stack) systems that used a gateway and a somewhat-thin client on the desktop.
Yes, there are a bunch of technological hurdles, none of which are easy to solve. And believe it or not, deploying and running a single version is not always possible. Custom macros, feature / function differences, desktop / color schemes, etc. all end up version-dependent, and sometimes you *can't* roll out a new version even when it's centrally managed.
In any event, what made these systems difficult to accept, customer-wise, was not the technology but the licensing.
How do you license it: by the computer, by the user, by the download? What about the server end -- by the processor, by the server? What about hot-failover clusters? What about the Internet -- do you really want to give access to anyone?
There was no simple way to license it, because no matter what you could think of, the customer had a different scheme they wanted to use. The sales force had no consistent pricing method, and since customers talk to one another, the pricing ended up all over the map.
We tried everything, including three "standard" pricing models that we thought would cover everything including a razor blade / handle model, and we still couldn't reach agreement with the customers on pricing.
Microsoft has these headaches all the time, just ask anyone who has dealt with desktop licenses, server licenses, CALs, and Terminal Server licenses for even a medium-smallish business. It will make your head spin. I doubt MS will come up with an equitable subscription service, especially for larger customers, because there are too many other licensing variables in there.
Once you decide on licensing, how do you regulate or enforce it? Tokens, passwords, thresholds, group memberships? Most customers resist active enforcement, preferring word-of-honor agreements and true-ups when necessary (such as with threat of audit).
The technology is solvable. The licensing is a muddle and is the biggest hurdle to overcome for these service-based proposals.
Sounds like this combines the productivity of meetings with the reliability and security of Microsoft applications. What's not to love?
Ignorance is the root of all evil.
Because of security reasons, there are plently of us that will NEVER be on the internet - ever.
There are plenty of us out here that must work in a realm where anonymity and the ability to purchase items with 100% zero strings attached is a first order requirement.
We pay for cash for all hardware and software, and we CAN NOT EVER "register" software because if we did, we'd go to jail. We can get updates from the internet, but its a 1-way street via sneakernet and a lot of shredded CD-Rs.
If/when Microsoft requires access and knowledge and subscriptions to software is the day we'll all switch to Linux and OpenOffice.
What kills me is, like always, instead of looking ahead proactively and seeing the path ahead, they will probably be forced to make a radical change at the end, and we'll be running on Windows 2000 until 2010. (NSA has NOT approved XP for desktop use, even though its being installed all over the place).
guns kill people like spoons make Rosie O'Donnell fat.
So what if MS comes up with a way to turn GPL software into Web-distributed applications which, in some twisted legal sense, they are installing on their computer which you just happen to be using...
Actually, the clinical definition of insanity resembles this (I'm paraphrasing):
The repetition of previous actions for which there is a known outcome with the expectation of a differing outcome.
You may want to commit that to memory.
I seem to recall there are already web-based office suites available - Hyperoffice comes to mind as one...
Microsoft announced they were going to provide Office through the Internet back in 1999 . I think it was called "Microsoft Office Online", but MS seems to have decided to use that name for a simple homepage about Office. I actually recall inadvertently running into a web page that was a web-based version of Outlook that ran through Internet Explorer years ago. It was sluggish, using DHTML for the GUI, although it looked identical to the desktop version.
I think Microsoft was doing this as a response to websites like HyperOffice that were cropping up at the time. I remember these sites were referred to as "Application Service Providers", although the definition of that term seems to have changed. I recall several but the sites don't seem to be up anymore. They were websites that provided a window manager within a browser. One was Desktop.com and another was Blox.com. Yahoo has a list of web-based desktop sites. There are some like GraphOn.com and WorkSpot.com that allow you to run remote desktops of actual operating systems through the web. WorkSpot seems sluggish, but Linux users might find it interesting to be able to access a Linux desktop through a Java Applet. There is a demo page that lets you try it out for 10 minutes.
When people don't want to worry about the security of their data moving across the 'net (I don't know why, seeing as how Microsoft products are so... ahem... secure... NOT!), or not being able to work when the network is congested or down, they will use something else. Open Office is one alternative (with the added benefit of being free, as in beer)... and for those who want to pay, Word Perfect is still out there...
So Microsoft, knock yourself out. There are other choices. Who knows, maybe after a taste of open source software, people will start using Linux more? ;-)
-- I ignore anonymous replies to my comments and postings.
...writing a resume. Would you like to: (a) be sacked for feeling up the secretary, disgraced, blackballed, and probably refused dole, or (b) erase the document, grovel to my office, and accept a pay cut?
I convinced my company to use Mediawiki at work for collaboration. We never looked back.
Offering Office as web services is a means to an end, and that end is collaboration. Deploying it as a web service on the Internet or on an intranet server will be a challenge, and we'll see how it works for Microsoft.
Collaboration is sorely needed even on the most basic things. It's not just for "time wasters" or beaurocrats. Even if I just want to document an important process or how some critical service was installed, it's seems like it's a herculean effort to publish and maintain such documents, among several people. And sometimes a document starts with only one person involved, and later it needs to be read and maintained by a whole group, all of a sudden.
In many companies we need simple things, like:
A content management system (CMS) deals with this sort of stuff. Oracle has a collaboration suite. There are many open-source CMS. SharePoint certainly tries to be a CMS. And there's Lotus Notes. But no CMS seems to dominate, and I haven't found one that is easy to implement and easy to use to share documents.
The real reason Office will be hosted online, is that Longhorn will require so much harddrive space to install, that you won't have room for any programs of your own. If you install a bigger hard drive, the swap file will immediaetly eat it up. :)
Microsoft has nasty habit they have of creating so-called "websites" that don't follow standards and won't run on anything but Windows, where they use the same entry points and callbacks that cause security problems for the native code. If I still have to use a Microsoft "browser", it does nothing for collaboration. In fact it makes the situations worse as you won't be able to use anything like Crossover anymore.
If I want a collaborative online environment, I use a webserver and CSS. Why would I want to go anywhere near a proprietary lock-in format just to share content? Why not WebDAV? ssh-ftp with a file manager hook ala Gnome? CVS?
My third concern is standalone operation. Just how in the world am I to do editing at a cabin, while travelling, or otherwise unable to connect at any kind of useful speed?
Not that it really matters, I guess, as I use Open Office for pretty much everything except Excel. They did do a nice job on the spreadsheet, and too many sheets have to use non-portable macros.
Eventually maybe Microsoft will clue in that "service model" does not mean the same thing as the old mainframe style "software rental." It's not a cash cow to keep sucking people's wallets, it's a way of providing flexible updates and maintenance as ongoing services instead of oft-delayed "service packs" or patches.
Besides, what makes Microsoft think I'd even think about letting their servers manage my document data? That stays right here in my managed environment where I know it's backed up and safe, thank-you-very-much!
I do not fail; I succeed at finding out what does not work.
"Consider this, if people subscribed to Office instead of the way it's done now, there'd be no more backward/forward compatibility problems. If MS updates the software, everybody's quickly up to date."
Also, if MS updates the software, everyone could be instantaneously file-incompatible with OpenOffice or whatever other competitor MS is worried about. If this beast really gets under way, MS could make it impossible for companies to *ever* get their data back and shift to other software.
Or, "This file is being edited by someone else for the next 62 hours, do you want to open a read-only copy?" Unfortunately, I expect the latter.
That's fine for the enterprise license holders which ( might ) be allowed to run the services on their network.
Problem is home users wont get that luxury, and will have to start renting their office suite, if they are going to stick with a Microsoft based suite.
But we all knew this day was coming so its no surprise. They will also move their OS to that same model, if they can find a way.
---- Booth was a patriot ----
Surely they will detect Firefox and make their servers show a gif of Clippo saying...
It looks like you're not using Internet Explorer.
Would you like help with installing IE, the world's best browser, as stated by our self-funded third-party research studies?
Because you can bet that Microsoft will be putting in a few hooks to do an online check to verify your OS and system license. They already hate Crossover, and would likely do just about anything to have them shut down.
They did the same thing to other products and companies, tweaking code so it wouldn't run on OS/2, or on other versions of DOS, or link with other compilers, or...
Their whole model is based on lock-in, not competition over quality, service, reliability, or price. Online services give them an excuse to check for DRM-enabled Windows clients, and refuse to allow anything else under the excuse that it's "not secure" or "unreliable". Heck, they'll probably even trot out some speech about the Patriot Act or DMCA as their "sound business reasoning".
I do not fail; I succeed at finding out what does not work.