More links on Microsoft’s FOSS War

•15May07 • 3 Comments

A few more articles worth reading on Microsoft’s anti-open-source FUD war.

First up is Jonathan Schwarz’s open letter with Free Advice for the Litigious, where he explains how Sun dealt with the open source competition. A choice quote:

With business down and customers leaving, we had more than a few choices at our disposal. We were invited by one company to sue the beneficiaries of open source. We declined. We could join another and sue our customers. That seemed suicidal. We were offered the choice to scuttle Solaris, and resell someone else’s operating system. We declined. And we were encouraged to innovate by developers and customers who wanted Sun around, who saw the value we delivered through true systems engineering.

Next up is Daniel Eran of RoughlyDrafted, who compares how Apple and Microsoft have approached open source, in Microsoft’s Unwinnable War on Linux and Open Source. He has some particularly harsh things to say about the Mono project, which I think are overstated. But there also is a strong kernel of truth in there:

We already know that Mono development exists at the whim of Microsoft, and that dangerous looking stalactites of patent threats point down from above. Mono developers insist that Microsoft is a changed company and would never let anything bad happen to developers working to extend the features of its .Net.

Microsoft’s own icy embrace of Mono developers is to offer a license that allows them to do anything but offer commercial software. Mono is nothing more than a training camp on how to serve Microsoft that leads to a do or die diploma ceremony at the end.

Finally we have Steven O’Grady of Redmonk doing one of his trademark Q&A discussions. Its great stuff, and though he does try to walk a fine to not offend Microsoft (one of his customers), in the end it seemed pretty clear how dismayed he was by this move on Microsoft’s part:

Microsoft has spent the past few years rehabilitating – at great expense and great effort – a highly negative public image. One that, importantly, did not terribly impact its ability to do business, but one that left the firm with very few defenders and advocates. It was, in many respects, the least loved firm in the industry.

While the Microsoft of the past year or so was certainly not beloved, it had gone some distance to changing the minds of many, persuading even some ardent critics that they’d learned a great deal from their past behaviors and emerged as a more responsible corporate player. Agree or disagree, articles describing the new “kinder, gentler” Microsoft abounded.

And then there was yesterday. Depending on how Microsoft proceeds from the statements made to Fortune, I could see virtually all of that hard won goodwill evaporating overnight. Whether their business is as immune to the negative sentiment as it was in the past remains to be seen, but I know that if I intended to compete with social movements – as Microsoft obviously intends to – I’d be trying to make friends, not enemies.

I think that says it all. My fearless prediction is that 5-10 years from now people will look back at yesterday and see it as one of the pivotal moments of the software industry, one where Microsoft turned their own customer base against them.

[Update 12:54 Pacific] Eben Moglen of the Free Software Foundation explains the Microsoft threat far better than I ever could:

[Update 05-16-07 10:49 Pacific] One more good link: Andy Updegrove does another Q&A.

Microsoft: Still evil after all these years, yea…

•14May07 • 12 Comments

(Apologies to Paul Simon…)

So by now everyone has probably heard about the latest round of FUD emanating from Redmond, claiming that Linux et al violate 235 Microsoft patents. The most amusing yet direct response is undoubtedly that of Sun’s Tim Bray:

Litigate or shut up.

Speaking only for myself and not for Adobe (as always, but in this case I want to emphasize it particularly), I think this latest move by Microsoft is proof positive that for all of their claimed moves towards more openness, Microsoft is still just as evil as they ever were. Does it really matter if they submit OOXML and XPS to standards bodies if they attack the open source operating systems and applications that implement those standards? Does having evangelists who promote interoperability and open source mean anything when they turn around and attack the vendors they are supposed to interoperate with? This is a sad day for the industry. I guess the big news here is that at least Microsoft is attacking more directly now instead of hiding behind SCO. All in all, a sad day.

Of course, this also makes me even happier that I escaped the Redmond orbit and found my way to Adobe. Here’s a summary of recent moves on the openness front by the two companies, which to me speak volumes:

Adobe Microsoft
Turned PDF Specification over to ISO via AIIM Promises to turn XPS over to ECMA or equivalent for rubber-stamping someday soon.
Donated Flash Player’s Tamarin JavaScript engine to Mozilla Open sourced their thin “DLR” that sits on top of their .Net runtime, but the license isn’t GPL compatible or compatible with OSI’s Open Source Definition.
Open sourced our Flex runtime and our Javascript & MXML compilers. C# and XAML compilers for Silverlight are closed source, as are the .Net runtime libraries.
Flash Player runs on Linux and Solaris. Silverlight doesn’t and won’t anytime soon. Novell’s MONO folks are developing their own version, but what Microsoft patents are they likely to run afoul of? We know Microsoft has warned other developers off of building XAML-based engines previously (c.f. xamlon).
Apollo developers are doing extensive work on WebKit, beefing up its Windows support in particular. IE still sucks.

Here’s some other interesting reading:

  • O’Reilly Network’s take on the announcement: “However, today’s news brings the major reason you should run away from depending on Microsoft technology like it had a case of Ebola.”
  • Joe Wilcox of Microsoft Watch says: “Microsoft should carefully consider its allegations. SCO hasn’t done as well as hoped with its Linux patent infringement claims, and the company came out swinging with a lineage of recognizable Unix patents. Meanwhile, the U.S. Supreme Court is pushing back against patent lawsuits.”
  • Simon Phipps of Sun says: “Very sad that they can’t work with the emerging paradigm like the rest of us instead of fighting it. No wonder so many developers hate them.”
  • Mike Gunderloy, formerly of long-time Microsoft developer, posted an article before the news hit talking about software patents where he said “Microsoft itself is built on open intellectual property from the first three or four decades of computer science.” How apt and ironic.
  • Mary Jo Foley says “What’s got Microsoft so spooked? As the Fortune article noted, the GPL v3’s provisions regarding the Microsoft-Novell deal suggest that Microsoft itself could be considered a ‘Linux distributor,’ and thus beholden to the GPL v3 terms. And even if that doesn’t happen, under the GPL v3, other Linux distributors would be barred from doing deals like the one struck by Novell and Microsoft.”
  • [Update 5:03pm] Via Stefan Tilkov, Charles Nutter says: “I’d hate to be an OSS developer or apologist at Microsoft today. If Sun did something like this I’d resign.”

Silverlight 1.1: No Love for PPC Macs

•07May07 • 26 Comments

John Lam of Microsoft has written a nice blog post called “Clearing the air about Silverlight and the DLR”. In it, he confirms that the final version of Silverlight 1.1 will not support PowerPC Macs:

  • 9. Silverlight V1.1 will only target Intel Mac OS X machines.

This is unfortunate but not surprising. Making .NET work on PowerPC would cost Microsoft time and money. According to this report, Apple sold 17.2 million PowerPC Macs running OS X between 2001 and 2005. Numbers for Intel Macs are a little less clear but seem to be in the 10-12 million range. Bottom line is that they’re blowing off half of the Mac installed base for the sake of their programmers’ convenience. Guess Bruce Chizen was right to question their commitment to cross-platform, huh?

On a more positive note, John Lam’s post also reveals that the new JScript implementation from Microsoft targets ECMAScript 3, which is the same version of ECMAScript supported by Flash Player. It’s great to see Microsoft doing something positive w.r.t. JavaScript/ECMAScript after ignoring it for so long (the ECMAScript 3 standard was published in 2001), even if they are just following our lead. Maybe Microsoft will even start contributing to ECMAScript 4 efforts soon…

Jeremy Zawodny on Silverlight

•04May07 • Comments Off on Jeremy Zawodny on Silverlight

Jeremy Zawodny of Yahoo has written a great post about Silverlight and what it means to the industry. Its probably the best thing I’ve seen written from a neutral point of view. I couldn’t agree more with his last two paragraphs:

Now don’t be fooled into thinking I believe that Silverlight will take over the web. I think it’s success as even a Flash killer is highly uncertain at this point. But it’s certain to be a big hit inside companies that have major investments in .NET technologies. That’s an awful lot of companies and an awful lot of code. But how much we’ll see Silverlight being used in “consumer” services is a whole different question.

Either way, this will have some pretty interesting ripple effects.

I agree with him that Silverlight 1.1 will have a lot of appeal within Microsoft’s strong developer base, many (if not most) of whom are already familiar with .NET programming. Those folks will still have a fair bit to learn going from the world of Windows.Forms to a more declaritive, web-style method of programming UIs, but it is less of a leap than going from that world into the full world of web-based programming.

The real question, as Jeremy points out, is whether Microsoft can break out of their existing base and capture a significant amount of business from other markets: designers, non-Microsoft web developers, Flash/Flex developers, etc. These are areas where Adobe has traditionally been stronger than Microsoft. We’re facing the same battle from the other side: can Adobe gain a significant number of developers from Microsoft’s base of programmers while holding them off in the markets we already do well in? You can guess which way I’m betting, but no matter what happens, the next few years are going to be very exciting.

Here are a couple more interesting perspectives on the competitive situation:

[Update 4May2007 14:37] A couple more interesting links to check out: