Miguel de Icaza Quotations

.NET was a company-wide branding effort at Microsoft that spanned multiple projects.

I think that by October the whole company has to migrate to OpenOffice, and then I think it's by June next year we all migrate to Linux - you don't want to migrate 6,000 people both operating system and office suite in a single jump.

We have a lot of existing customers which are also considering Linux desktop migrations and rolling out some of these programs, so we're learning from them.

We're doing Mono because we care about upgrading the development platform, we care about language independence; and it's very nice two work on.

But .NET is a really nice platform to build on.

We all love Linux, but it's also a fact that some people might not be able to migrate.

At Novell, we have set up a continuous build process for Mono and its tools that not only builds Mono, but also runs an extensive test suite.

Running the test suite like this allows us to catch problems when they are just introduced.

After releasing Mono 1.0, we started work on a new edition of Mono that will be released later in the year.

All of our code is open source, so it can be used for other projects.

They have a beautiful security system and we're emulating the whole security infrastructure.

It's strategic for us - lots of people will develop applications in .NET.

In the GNOME project we tried to keep the platform language independent.

In some cases we've been building tools that are specific to Linux for the desktop, and they only work on Linux, but I see two major projects that are wildly, wildly successful: Mozilla and OpenOffice, and those two programs are cross platform.

In addition to that, Mono has produced a very large set of extra libraries.

I was interested in Java the beginning, but the problem with Java is you do have to switch your platform.

Every piece of software written today is likely going to infringe on someone else's patent.

We cannot choose one desktop over the other - Gnome or KDE - because there's users for both code bases.

Our strategy in dealing with patents in Mono is the same strategy that any other software developer would take. In the event of a patent claim, we will try to find prior art to the claim of the patent.

Not to go too far, but Microsoft is probably used by most people out there

The software patent problem is not limited to Mono. Software patents affect everyone writing software today.

We've been using C and C++ way too much - they're nice, but they're very close to the machine and what we wanted was to empower regular users to build applications for Linux.

We could refresh the look and feel of the entire desktop with Moonlight

I believe in true love. But I am easily satisfied.

So if we're going to build new applications that require a large time investment, like say movie editing - today that doesn't matter for the enterprise desktop, but eventually it will when we get closer to consumers - you really need to have a cross-platform story.

Some scientists use TeX or LatEX but for most people Word is the thing that writers use these days.

When it comes to .NET they've done a really outstanding job.

With .NET once an API is published it's available to all programming languages at the same time.

There is a point in your life when you realize that you have written enough destructors...

Well Microsoft really does develop some really interesting technology.