Canonical announced yesterday that Matt Asay was taking over as the new COO.
Matt, whose employment history includes Novell and Alfresco, makes the announcement of his new job on his CNET blog.
To give you an idea of how he thinks this post, Free Software is Dead. Long Live Open Source, should help. It is also very helpful to read the comments to that blog article. In support of his view, Matt quotes Jasen Perlow:
Before you jump down Jason's throat, read what he had to say a month ago about Windows 7.
Anyway, I disagree that "interoperability" is a problem created by FOSS & the GPL. Interoperability would not be a problem IF proprietary software houses wrote their software to conform with un-encumbered and truly OPEN software standards, unlike the EMCA 334 & 335 standards that MONO is written to.
Also, Glyn Moody, in the Linux Journal, replied to Matt's article. Glyn's article can be summarized by this quote:
Despite all his work in with various Linux companies, Matt says he is a Mac Fan who claims he "has a bias against" 20th Century proprietary software models, what ever that means.
I've read (but can no longer find the URL in Mark's blog) that Mark Shuttlesworth has spent more than $40 million dollars on Canonical in an attempt to make it financially self supporting. He has done a magnificent job in marketing Ubuntu and making it the world's leading Linux distro, but he hasn't made Canonical self-sustaining. That will be Jane Silber and Matt Asay's job, especially Matt's, because of his marketing background.
My personal prediction is that Matt will continue the MONO push on Ubuntu, perhaps expanding it to incorporate de Icaza's dream of making a Linux desktop built entirely out of MONO/Moonlight (a.k.a. .NET/SilverLight) that talks directly to Linux kernel through the libc6 API. They could even bypass the libc6 in favor of a C# build API that leaves the Linux kernel as the only piece of the distro that remains unencumbered by the threat of a Microsoft IP lawsuit.
I can see Asay thinking that by using .NET applications running under MONO as the application base, he can use Microsoft technology to compete against Microsoft technology. The only fly in that ointment will be when Microsoft does to a MONO desktop what they did to the Apple Mac/iPod MONO application market -- modifying SilverLight 4 to use their patented COM technology, making it incompatible with applications using the previous versions of .NET and SilverLight. The fact that MONO is now incorporating MS IP not in the EMCA 334 & 335 standards will become as a future roadblock when Microsoft decides it is time to "cut off" Canonical's air supply (.NET technology in MONO). This will set back or even destroy Canonical. Besides, it raises a point that Shuttlesworth made about using Windows API on the Linux desktop, quoted in my email sig:
How does Canonical help Kubuntu? I've never read anything by Canonical that spells out exactly how they manage or help Kubuntu. I imagine that "some" Ubuntu developers split part of their work week between Ubuntu and Kubuntu. Canonical owns the Kubuntu trademark. Canonical pays to send out Kubuntu LiveCD for free to users who request them. But, they don't market Kubuntu the way they do Ubuntu. Canonical pays for the server space for Kubuntu development and downloads. The bandwidth bill can get rather large. They help LoCo teams, but not financially. The Chicago Ubuntu filed Chapter 13 a month ago. While Canonical doesn't appear to spend nearly as much on Kubuntu as they do on Ubuntu, I have no doubt that they could save a good chunk of money by dropping Kubuntu altogether and focusing entirely on Ubuntu/MONO. I wouldn't be surprised if they did.
We'll soon find out.
Matt, whose employment history includes Novell and Alfresco, makes the announcement of his new job on his CNET blog.
To give you an idea of how he thinks this post, Free Software is Dead. Long Live Open Source, should help. It is also very helpful to read the comments to that blog article. In support of his view, Matt quotes Jasen Perlow:
But some people, particularly our free software leaders, are so mired in their hatred of Microsoft and proprietary systems that they will use only free and open source software for the sake of ideological reasons alone....Stallman and the FSF [Free Software Foundation], like his Cretaceous ancestors 65 million years ago, isn't evolved enough to see that his reign is about to come to an end. The open world needs interoperability, not shut itself off from other standards just because they originate from proprietary sources.
Anyway, I disagree that "interoperability" is a problem created by FOSS & the GPL. Interoperability would not be a problem IF proprietary software houses wrote their software to conform with un-encumbered and truly OPEN software standards, unlike the EMCA 334 & 335 standards that MONO is written to.
Also, Glyn Moody, in the Linux Journal, replied to Matt's article. Glyn's article can be summarized by this quote:
Ultimately, the reason that free software cannot compromise is because we compromise over any freedom at our peril: there is no such thing as 50% free. As history teaches us, freedom is not won by “going mainstream”, but by small numbers of stubborn and often annoying monomaniacs that refuse to compromise until they get what they want. The wonderful thing is that we can all share the freedoms they win, whether or not we helped win them, and whether or not we can live up to their high standards of rigour.
I've read (but can no longer find the URL in Mark's blog) that Mark Shuttlesworth has spent more than $40 million dollars on Canonical in an attempt to make it financially self supporting. He has done a magnificent job in marketing Ubuntu and making it the world's leading Linux distro, but he hasn't made Canonical self-sustaining. That will be Jane Silber and Matt Asay's job, especially Matt's, because of his marketing background.
My personal prediction is that Matt will continue the MONO push on Ubuntu, perhaps expanding it to incorporate de Icaza's dream of making a Linux desktop built entirely out of MONO/Moonlight (a.k.a. .NET/SilverLight) that talks directly to Linux kernel through the libc6 API. They could even bypass the libc6 in favor of a C# build API that leaves the Linux kernel as the only piece of the distro that remains unencumbered by the threat of a Microsoft IP lawsuit.
I can see Asay thinking that by using .NET applications running under MONO as the application base, he can use Microsoft technology to compete against Microsoft technology. The only fly in that ointment will be when Microsoft does to a MONO desktop what they did to the Apple Mac/iPod MONO application market -- modifying SilverLight 4 to use their patented COM technology, making it incompatible with applications using the previous versions of .NET and SilverLight. The fact that MONO is now incorporating MS IP not in the EMCA 334 & 335 standards will become as a future roadblock when Microsoft decides it is time to "cut off" Canonical's air supply (.NET technology in MONO). This will set back or even destroy Canonical. Besides, it raises a point that Shuttlesworth made about using Windows API on the Linux desktop, quoted in my email sig:
"If Windows API becomes the default on Linux then what is the point of Linux?" -- Mark Shuttlesworth
MONO is Windows API
MONO is Windows API
We'll soon find out.
Comment