A Quote by Miguel de Icaza

All of our code is open source, so it can be used for other projects. — © Miguel de Icaza
All of our code is open source, so it can be used for other projects.
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.
In open source, you really have to be near the watershed to have an impact on the source code. Customers want to be near the key contributors to the code, not a level removed.
The Open Source theorem says that if you give away source code, innovation will occur. Certainly, Unix was done this way... However, the corollary states that the innovation will occur elsewhere. No matter how many people you hire. So the only way to get close to the state of the art is to give the people who are going to be doing the innovative things the means to do it. That's why we had built-in source code with Unix. Open source is tapping the energy that's out there.
If an open source product gets good enough, we'll simply take it. So the great thing about open source is nobody owns it - a company like Oracle is free to take it for nothing, include it in our products and charge for support, and that's what we'll do. So it is not disruptive at all - you have to find places to add value. Once open source gets good enough, competing with it would be insane. We don't have to fight open source, we have to exploit open source.
The main languages out of which web applications are built - whether it's Perl or Python or PHP or any of the other languages - those are all open source languages. So the infrastructure of the web is open source... the web as we know it is completely dependent on open source.
Open-source code is extremely well-adapted to service-oriented architecture.
You can't trust code that you did not totally create yourself. (Especially code from companies that employ people like me.) No amount of source-level verification or scrutiny will protect you from using untrusted code.
There were open source projects and free software before Linux was there. Linux in many ways is one of the more visible and one of the bigger technical projects in this area, and it changed how people looked at it because Linux took both the practical and ideological approach.
As a kid I used to love going to open houses and doing DIY projects with my parents and sister around our home.
Always think about how a piece of code should be used: good interfaces are the essence of good code. You can hide all kinds of clever and dirty code behind a good interface if you really need such code.
One of the questions I've always hated answering is how do people make money in open source. And I think that Caldera and Red Hat - and there are a number of other Linux companies going public - basically show that yes, you can actually make money in the open-source area.
No matter what, the way to learn to program is to write code and rewrite it and see it used and rewrite again. Reading other people's code is invaluable as well.
What I do for a living is somewhat like mercenary prostitution. I spend a lot of energy trying to find games to bring to alternate platforms, like Linux and MacOS, and in my free time, I work on various open source projects, and other freebies like that. So I guess I'm a hooker with a heart of gold, sorta.
There's a definite sense this morning on the part of the Kerry voters that perhaps this is code, 'moral values,' is code for something else. It's code for taking a different position about gays in America, an exclusionary position, a code about abortion, code about imposing Christianity over other faiths.
In the world of digital currencies, the social network around open source projects has become a critical test bed for ideas, products, services, and early users.
If the DHS insists, as bureaucracies are apt to do, that open-source must be certified via a sanctioned, formal process, it will interfere with the informal process of open-source itself. It seems to me the DHS is trying to turn an open-source development project into a Microsoft (or IBM or Oracle) software development project. And we know what that means: more, not fewer, errors -- security and otherwise.
This site uses cookies to ensure you get the best experience. More info...
Got it!