“Sharing the code just seems like The Right Thing to Do, it costs us rather little, but it benefits a lot of people in sometimes very significant ways. There are many university research projects, proof of concept publisher demos, and new platform test beds that have leveraged the code. Free software that people value adds wealth to the world.”

— John D. Carmack

Quoted in Brad Cook, "John Carmack: Making the Magic Happen" http://www.apple.com/games/articles/2009/02/johncarmack/ Apple.com

Adopted from Wikiquote. Last update Aug. 20, 2022. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Sharing the code just seems like The Right Thing to Do, it costs us rather little, but it benefits a lot of people in s…" by John D. Carmack?

John D. Carmack31

American computer programmer, engineer, and businessman 1970

Related quotes

“This might hurt a little is universal code for this will definitely hurt a lot”

Eoin Colfer (1965) Irish author of children's books

Source: The Last Guardian

“The programmers who write improvements to GCC (or Emacs, or Bash, or Linŭ, or any GPL-covered program) are often employed by companies or universities. When the programmer wants to return his improvements to the community, and see his code in the next release, the boss may say, "Hold on there — your code belongs to us! We don't want to share it; we have decided to turn your improved version into a proprietary software product."
Here the GNU GPL comes to the rescue. The programmer shows the boss that this proprietary software product would be copyright infringement, and the boss realizes that he has only two choices: release the new code as free software, or not at all. Almost always he lets the programmer do as he intended all along, and the code goes into the next release.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

1990s, Copyleft: Pragmatic Idealism (1998)

“It was a rather extraordinary conversation if you think about it -- both of us speaking in code. But not military code, not Intelligence or Resistance code -- just feminine code.”

Elizabeth Wein book Code Name Verity

Source: Code Name Verity

“The Code-and-Fix Model. The basic model used in the earliest days of software development contained two steps:
:1. Write some code.
:2. Fix the problems in the code.
Thus, the order of the steps was to do some coding first and to think about the requirements, design, test, and maintenance later. This model has three primary difficulties: (a) After a number of fixes, the code became so poorly structured that subsequent fixes were very expensive. This underscored the need for a design phase prior to coding. (b) Frequently, even well designed software was such a poor match to users' needs that it was either rejected outright or expensively redevelopment…”

Barry Boehm (1935) American software engineer

Source: A spiral model of software development and enhancement. (1988), p. 61-62

“You see, some people have a talent for programming. At ten to thirteen years old, typically, they're fascinated, and if they use a program, they want to know: “How does it do this?” But when they ask the teacher, if it's proprietary, the teacher has to say: “I'm sorry, it's a secret, we can't find out.” Which means education is forbidden. A proprietary program is the enemy of the spirit of education. It's knowledge withheld, so it should not be tolerated in a school, even though there may be plenty of people in the school who don't care about programming, don't want to learn this. Still, because it's the enemy of the spirit of education, it shouldn't be there in the school.
But if the program is free, the teacher can explain what he knows, and then give out copies of the source code, saying: “Read it and you'll understand everything.” And those who are really fascinated, they will read it! And this gives them an opportunity to start to learn how to be good programmers.
To learn to be a good programmer, you'll need to recognize that certain ways of writing code, even if they make sense to you and they are correct, they're not good because other people will have trouble understanding them. Good code is clear code that others will have an easy time working on when they need to make further changes.
How do you learn to write good clear code? You do it by reading lots of code, and writing lots of code. Well, only free software offers the chance to read the code of large programs that we really use. And then you have to write lots of code, which means you have to write changes in large programs.
How do you learn to write good code for the large programs? You have to start small, which does not mean small program, oh no! The challenges of the code for large programs don't even begin to appear in small programs. So the way you start small at writing code for large programs is by writing small changes in large programs. And only free software gives you the chance to do that.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

A Free Digital Society - What Makes Digital Inclusion Good or Bad? http://www.gnu.org/philosophy/free-digital-society.html#education; Lecture at Sciences Po in Paris (19 October 2011)] <br class="br">2010s

“Releasing Linux versions has always been a matter of higher code quality, good software architecture, and technical interest for the platform.”

Timothee Besset French software programmer

Quoted in Maxim Bardin, "id Software and Linux – By TTimo" http://linuxgamingnews.org/2009/09/15/id-software-and-linux-by-ttimo/ Linux Gaming News (2009-09-15).

“The real value of tests is not that they detect bugs in the code, but that they detect inadequacies in the methods, concentration, and skills of those who design and produce the code.”

C. A. R. Hoare (1934) British computer scientist

How Did Software Get So Reliable Without Proof? Lecture Notes in Computer Science vol 1051 1996 pp. 1-17 : FME '96: Industrial Benefit and Advances in Formal Methods, Third International Symposium of Formal Methods Europe, Co-Sponsored by IFIP WG 14.3, Oxford, UK, March 18-22, 1996, Proceedings.

“We are a non-utopian political movement. We are not interested in going nowhere. We are not interested in going to some place we have never been, which we will get to after the revolution because people will be different.
The crucial operating premise of the Free Software Movement as a revolutionary politic is: Proof of Concept plus Running code. Here. We did it already. It's sort of working. If you take a copy and help us fix it, it could really be something. Here. You want it? Take it. We like it.
It's Free.”

Eben Moglen (1959) American law professor and free software advocate

Talk at Seattle University, March 13 2009 http://www.youtube.com/watch?v=tbcy_ZxXLl8

“The present molders of the code seemed to have a clear knowledge of just how difficult to make something, to add to its fascination, without making it impossible.”

Lester del Rey (1915–1993) Novelist, short story writer, editor

Source: The Eleventh Commandment (1962), Chapter 5 (p. 42)

“For example, the GPLv2 in no way limits your use of the software. If you're a mad scientist, you can use GPLv2'd software for your evil plans to take over the world ("Sharks with lasers on their heads!!"), and the GPLv2 just says that you have to give source code back. And that's OK by me. I like sharks with lasers. I just want the mad scientists of the world to pay me back in kind. I made source code available to them, they have to make their changes to it available to me. After that, they can fry me with their shark-mounted lasers all they want.”

Linus Torvalds (1969) Finnish-American software engineer and hacker

Linux Licensing, Forbes, 2006-03-09, Lyons, Daniel, 2006-08-28 http://www.forbes.com/technology/2006/03/09/torvalds-linux-licensing-cz_dl_0309torvalds1.html, <br class="br">2000s, 2006

Help us to complete the source, original and additional information

John D. Carmack31

Related quotes

Related topics