Skip to main content

Novell sues Microsoft for sinking WordPerfect (revised)

Oh come on now.... we all know who sank WordPerfect and it certainly wasn't Microsoft.

(Craig set me right in his comments too - Noorda did a similar thing , overpaying for a product that was long in the tooth and then just calling in the lawyers. How much did Borland end up buying dBase for? They at least waited until the product was pretty much history in so far as being a market leader. There's something to be said about picking the right battles...)

It was Corel (among others) biting off more than they could chew with an owner (a certain Mr. Michael Cowpland) who made grandiose statements that couldn't be kept. Cowpland is a great visionary but he couldn't manage Corel at that size and he made a TERRIBLE mistaking buying a product like WordPerfect that simply hadn't kept up with the times.

Yes - there are secrets in Windows that maybe MS should be more open about - but to say they SANK WorkPerfect? WordPerfect was beginning to become a terrible product in the very first version of the Windows product - before Novell even owned it. I remember trying to save a basic document with some images and having it grow double the size each time. Let me guess - that was Microsoft Word secretly adding code into the Wordperfect file...

Unbelievable...

Novell sues Microsoft for sinking WordPerfect | Tech News on ZDNet

Comments

Game Geek said…
You're right and wrong. You're right that it wasn't Microsoft. Here's where you're wrong: WordImperfect was gone long before Novell sold it off to Cowpland and Corel. Ray Noorda, the former head honcho at Novell should take much of the blame. He had to fight Microsoft on everything, every step of the way. He's the one that overpaid to buy WordImperfect and then made the wrong decisions fighting Microsoft. Fighting things in court has long been Noorda's trademark. Even though he's no longer at Novell, his legacy and management style live on.
Andrew MacNeill said…
That's right Craig! There's something to be said about picking the right battles...

Intuit picked the right battle with Microsoft and they beat Money with Quicken regularly...

Mozilla is now doing it with Firebox...

But to go after Microsoft's crown jewel essentially guarantees a messy battle...
Ted Roche said…
Microsoft has already admitted and been convicted of unlawful business practices. This is just the civil portion of that process, paying damages for the crimes committed.

There's no question that Novell, Lotus, Corel and many other software shops had only themselves as their worst enemy. Bad judgements, poor quality, poor technical support killed most of these companies. But competing against a monopoly that went out of their way to hide APIs and "cut off the oxygen supply" of their competitors certainly didn't help.

Microsoft is doing a fine job of serving their stockholders in paying off and settling these claims for pennies on the dollar out of court, and at the same time, gaining valuable compromises, like the agreement by Novell to withdraw as claimant in the European Union's antitrust investigation against Microsoft. Between that, the new stock option plans Microsoft got approved, and the dividend payoff to its stockholders, Microsoft will shake off the 90s and come out a significantly different company. I think things are going as well as Microsoft could possibly hope.
Andrew MacNeill said…
Good point, Ted. If MS had been more open in their competitive practices from day one, then they would actually have been able to use the billions they are spending today on lawsuits.

I don't see anything wrong with two large companies getting together and saying "I go after this slice of the pie, you go after that one and between us, we'll squeeze out the competion" - as long as they do it fairly and openly. But when they then create contracts and practices designed to limit the consumers choices (exclusive branding for certain vendors so they can't - not won't - offer other alternatives) - then that is simply a monopolistic lawsuit in the waiting. Even smaller companies who do it should be barred from doing so. Because if they get bigger (as MS did), then they are just asking for trouble...

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP