Miguel de Icaza Quotes

A new release of Plan 9 happened in June, and at about the same time a new release of the Inferno system, which began here, was announced by Vita Nuova.

We have a rule that if you check in code, you have to maintain it. So I mostly code on the side. I don't check in code anymore.

Many people think that open source projects are sort of chaotic and and anarchistic. They think that developers randomly throw code at the code base and see what sticks.

We plan to support Exchange 2003 as soon as it is released. We already have the prerelease versions from MSDN.

It's important not only to have the right timing of when the hardware is going to be released but also when we are going to be able to introduce quality software.

In true open source development, there's lots of visibility all the way through the development process.

There is no schedule. We are all volunteers, so we get it done when we get it done. Perl 5 still works fine, and we plan to take the right amount of time on Perl 6.

We ship a new version of Google Play Services every six weeks. Typically, 90 percent of users are on the new version of that.

The problem is, in software design, often the consequences of your decisions don't become apparent for years.

The Mozilla project is big in terms of lines of code and complexity.

There's innovation in Linux. There are some really good technical features that I'm proud of. There are capabilities in Linux that aren't in other operating systems.

The beauty of open-source is that you can pick up right where someone left off and start right there.

The interesting thing about Android's design is how little we modified the kernel.

My list of basic tools is a partial answer to the question about what has changed: Over the past few years, large numbers of programmers have come to depend on elaborate tools to interface code with systems facilities.

We've always been the development project that lived in a time pressured setting and always where commercial entities were relying heavily on releases in a certain time frame.

Cosmoe is nearing the stage where I would feel comfortable doing a preliminary release aimed at developers.

When I first got into technology I didn't really understand what open source was. Once I started writing software, I realized how important this would be.

There are two main methodologies of open source development. There's the Apache model, which is design by committee - great for things like web servers. Then you have the benevolent dictator model. That's what Ubuntu is doing, with Mark Shuttleworth.

Not only because the product wasn't a great product, but remember it took us five or six years to ship it. Then we had to sort of fix it. That was what I might call Windows 7.

Release early and often.

I never got into Linux. I swear to God, it's only lack of time. I'm past the years of my life where I can really dig into something like running a Linux system. I'm very sympathetic to the whole idea; Linux people always think the way I want to think.

In programming when you're making a change you have to know all the affected places, and you have to be able to model in your head what the performance impact will be.

I think making features has got to be in the addiction category.

I don't actually follow other operating systems much. I don't compete - I just worry about making Linux better than itself, not others.

Once open source gets good enough, competing with it would be insane.