Interview with Electronics magazine (1989)
1980s
Quotes about software
page 3
In Amrita Ghosh, "Author in Focus: An Interview with Dalrymple".
That was s, uh — that was the end of that conversation.
Speech to the Economic Club of Detroit (1997) https://www.youtube.com/watch?v=OzX6UUJ461s
1990s
Edward V. Berard (1998) " Metrics for object-oriented software engineering http://www.ipipan.gda.pl/~marek/objects/TOA/moose.html." The Object Agency, Inc.
D.T. Ross (1989) "Appendix B: Understanding: The Key to Software" in: Computer Science and Telecommunications Board, National Research Council Scaling Up: A Research Agenda for Software Engineering. p. 66 (cited on p. 3).
2006 interview in Business Week, cited in: Rebutting Clayton Christensen on Apple's 'Troubled' Future http://seekingalpha.com/article/5633-rebutting-clayton-christensen-on-apples-troubled-future-aapl-msft-dell in Seeking Alpha (11 January 2006)
2000s
1990s, Why "Free Software" is better than "Open Source" (1998)
Quoted in "Functional programming in C++" http://gamasutra.com/view/news/169296/Indepth_Functional_programming_in_C.php
Source: Model-driven development of complex software: A research roadmap (2007), p. 37: Introduction
Source: A spiral model of software development and enhancement. (1988), p. 63
“I think the open software movement (and Linux in particular) is laudable.”
"Ken Thompson clarifies matters", 1999
Source: Executable Uml: A Foundation for Model-Driven Architecture, 2002, p. 10.
August-Wilhelm Scheer, and Frank Habermann. " Enterprise resource planning: making ERP a success http://ecis.seattleu.edu/courses/ecis464spring04/Articles/Making%20ERP%20a%20Success.pdf." Communications of the ACM 43.4 (2000): 57-61.
2000s, Thus Spake Stallman (2000)
Edward A. Shanken. Systems https://books.google.nl/books?id=Ip_0rQEACAAJ, 2015. Overview
Minus 24x http://www.monochrom.at/minus24x/index-eng.htm, 2001
Source: Model-driven development of complex software: A research roadmap (2007), p. 37: Abstract
TechCrunch Interview With Steve Ballmer http://youtube.com/watch?v=1OpRQMRa270 in YouTube (24 September 2009)
2000s
Source: Retrospectives : The Early Years in Computer Graphics at at MIT, Lincoln Lab and Harvard (1989), p. 26.
Source: Just a Theory: Exploring the Nature of Science (2005), Chapter 4, “Falsificationism: If It Might Be Wrong, It’s Science” (p. 69)
“Brooks's Law: Adding manpower to a late software project makes it later.”
Page 25 (italics in source, bold added).
The Mythical Man-Month: Essays on Software Engineering (1975, 1995)
Source: Collective Intelligence and its Implementation on the Web (1999), p.253
Grady Booch, Robert A. Maksimchuk, Michael W. Engle (2007) Object-Oriented Analysis and Design with Applications Chapter 6.
Interview with Dennis Bathory-Kitsz in 80 Microcomputing (1980) http://features.slashdot.org/article.pl?sid=00/01/20/1316236&mode=thread Clips from the interview can be found on "No Money (Lullaby for Bill)" http://maltedmedia.com/books/papers/sf-gates.html by Dennis Báthory-Kitsz. http://maltedmedia.com/people/bathory/index.html
1980s
Source: A spiral model of software development and enhancement. (1988), p. 61
Source: Learning to implement enterprise systems (2002), p. 18
more and louder than ever before.
1990s, Why "Free Software" is better than "Open Source" (1998)
Re: What obstacles do Common Lisp programmers face? http://groups.google.com/group/comp.lang.lisp/msg/47a3832fab496eda (Usenet article).
Usenet articles, Miscellaneous
command names, menu formats
L.M. Branscomb, J.C. Thomas (1984) "Ease of use: a system design challenge". in: IBM Systems Journal. Vol 23.3, Sept 1984. Pages 224-235
How I do my computing (2006) http://stallman.org/stallman-computing.html
2000s
“If the software doesn't have to work, you can always meet any other requirement.”
Source: Quality Software Management: Volume 2, First-order measurement, 1993, p. 111
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).
Upon receiving the Linus Torvalds Award at Linuxworld, (1999) http://www.youtube.com/watch?v=bDxMJQLXmBE
1990s
"How to Make Wealth" http://www.paulgraham.com/wealth.html, May 2004
Keynote Speech at FOSDEM 2007: Liberating Java http://ftp.belnet.be/mirrors/FOSDEM/2007/FOSDEM2007-Liberating-Java.ogg
James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35
1980s, GNU Manifesto (1985)
Tom DeMarco and Barry Boehm. " The agile methods fray http://cf.agilealliance.org/articles/system/article/file/872/file.pdf." Computer 35.6 (2002): 90-92.
“People who are really serious about software should make their own hardware.”
talk at Creative Think seminar, 20 July 1982 https://www.folklore.org/StoryView.py?project=Macintosh&story=Creative_Think.txt
1980s
ACM Queue A Conversation with Alan Kay Vol. 2, No. 9 - Dec/Jan 2004-2005 http://queue.acm.org/detail.cfm?id=1039523
2000s, A Conversation with Alan Kay, 2004–05
[Interview: Theo de Raadt on Industry and Free Software, http://en.epochtimes.com/news/5-7-5/30084.html, 2005-07-05, 2007-01-10, The Epoch Times]
2000s, Thus Spake Stallman (2000)
2000s, What is free software? (2006)
"Nerds 2.0.1 - A Brief History of the Internet", Part 3
Source: Software Engineering: Principles and Practice, 2007, p. 2
1978 Turing Award Citation https://web.archive.org/web/20070708004814/http://awards.acm.org/citation.cfm?id=4173633&srt=all&aw=140&ao=AMTURING.
About
"The next society" Economist.com http://www.economist.com/ (November 2001)
1990s and later
Source: Essays on object-oriented software engineering (1993), p. 5
Richard A. D’Aveni (1997). " Waking up to the New Era of Hypercompetition https://www.researchgate.net/publication/233454654_Waking_Up_to_the_New_Era_of_Hypercompetition". The Washington Quarterly, Sept. 3, 1997. p. 183–195. Lead paragraph.
Life 3.0: Being Human in the Age of Artificial Intelligence (2017)
Bill Gates Interview: Winner of the 1993 Price Waterhouse Leadership Award for Lifetime Achievement, Computerworld Smithsonian Awards, https://web.archive.org/web/20080501040344/http://americanhistory.si.edu/collections/comphist/gates.htm, May 10, 2008, National museum of American history - Smithsonian Institution, 1993, October 8, 2014 http://americanhistory.si.edu/collections/comphist/gates.htm,
1990s
Richard Stallman on Free Software: Freedom is Worth the Inconvenience, Stallman, Richard, 2016-04-01, 2019-04-07, Singularity Weblog https://youtube.com/watch?v=NB8mCcLRxlg&t=3077,
2016
“1,3,7-trimethylxanthine – a basic ingredient in quality software.”
Usenet signatures
"The Other Road Ahead" http://www.paulgraham.com/road.html, September 2001
1980s, GNU Manifesto (1985)
"If Books Were Sold as Software" http://www.newsscan.com/cgi-bin/findit_view?table=newsletter&dateissued=20040818#11200, NewsScan.com (18 August 2004)
If Books Were Sold as Software (2004)
Talk at Seattle University, March 13 2009 http://www.youtube.com/watch?v=tbcy_ZxXLl8
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)]
2010s
“Fight Features. … The only way to make software secure, reliable, and fast is to make it small.”
"Some Notes on the 'Who Wrote Linux' Kerfuffle", release 1.5 http://www.cs.vu.nl/~ast/brown/.
On the kde-licensing mailing list, (13 April 1998) https://marc.info/?l=kde-licensing&m=89249041326259&w=2
1990s
Source: Object-oriented design: With Applications, (1991), p. 142
Free Software and Beyond: Human Rights in the Use of Software", address at Goeteborg, Sweden (16 May 2007)
2000s
Context: To have the choice between proprietary software packages, is being able to choose your master. Freedom means not having a master. And in the area of computing, freedom means not using proprietary software.
“Free software permits students to learn how software works.”
Why Schools Should Exclusively Use Free Software (2003) http://www.gnu.org/education/edu-schools.html
2000s
Context: Free software permits students to learn how software works. Some students, on reaching their teens, want to learn everything there is to know about their computer and its software. They are intensely curious to read the source code of the programs that they use every day. To learn to write good code, students need to read lots of code and write lots of code. They need to read and understand real programs that people really use. Only free software permits this.
Proprietary software rejects their thirst for knowledge: it says, “The knowledge you want is a secret — learning is forbidden!” Free software encourages everyone to learn. The free software community rejects the “priesthood of technology”, which keeps the general public in ignorance of how technology works; we encourage students of any age and situation to read the source code and learn as much as they want to know. Schools that use free software will enable gifted programming students to advance.
May the Source Be With You (2001)
Context: While the creative works from the 16th century can still be accessed and used by others, the data in some software programs from the 1990s is already inaccessible. Once a company that produces a certain product goes out of business, it has no simple way to uncover how its product encoded data. The code is thus lost, and the software is inaccessible. Knowledge has been destroyed.
MEME 2.04, an interview with David S. Bennahum (1996) http://memex.org/meme2-04.html
1990s
Context: In 1971 when I joined the staff of the MIT Artificial Intelligence lab, all of us who helped develop the operating system software, we called ourselves hackers. We were not breaking any laws, at least not in doing the hacking we were paid to do. We were developing software and we were having fun. Hacking refers to the spirit of fun in which we were developing software. The hacker ethic refers to the feelings of right and wrong, to the ethical ideas this community of people had — that knowledge should be shared with other people who can benefit from it, and that important resources should be utilized rather than wasted. Back in those days computers were quite scarce, and one thing about our computer was it would execute about a third-of-a-million instructions every second, and it would do so whether there was any need to do so or not. If no one used these instructions, they would be wasted. So to have an administrator say, "well you people can use a computer and all the rest of you can't," means that if none of those officially authorized people wanted to use the machine that second, it would go to waste. For many hours every morning it would mostly go to waste. So we decided that was a shame. Anyone should be able to use it who could make use of it, rather than just throwing it away. In general we did not tolerate bureaucratic obstructionism. We felt, "this computer is here, it was bought by the public, it is here to advance human knowledge and do whatever is constructive and useful." So we felt it was better to let anyone at all use it — to learn about programming, or do any other kind of work other than commercial activity.
Source: UML Distilled: A Brief Guide to the Standard Object Modeling, 2004, p. xxvi
"Startup mines for riches in collaboration software" in The Portland Tribune (4 March 2008) http://www.portlandtribune.com/rethinking/story.php?story_id=120430910578805900
Context: When I was at Tek, I was frustrated that computer hardware was being improved faster than computer software. I wanted to invent some software that was completely different, that would grow and change as it was used. That’s how wiki came about.
The Art of Doing Science and Engineering: Learning to Learn (1991)
Context: The fundamentals of language are not understood to this day.... Until we understand languages of communication involving humans as they are then it is unlikely many of our software problems will vanish.
“Free Software in Ethics and Practice” talk at CMC MSU, Moscow, Russia, (3 March 2008) Text http://phobos.cs.msu.su/FTP/Stallman/rms-cmc.txt · ogg file http://sbos.in/RMS_Lection.ogg · YouTube http://youtube.com/watch?v=GrJpXJY4Oow
2000s
Context: Isn't it ironic that the proprietary software developers call us communists? We are the ones who have provided for a free market, where they allow only monopoly. … if the users chooses this proprietary software package, he then falls into this monopoly for support … the only way to escape from monopoly is to escape from proprietary software, and that is what the free software movement is all about. We want you to escape and our work is to help you escape. We hope you will escape to the free world. The free world is the new continent in cyberspace that we have built so we can live here in freedom. It's impossible to live in freedom in the old world of cyberspace, where every program has its feudal lord that bullies and mistreats the users. So, to live in freedom we have to build a new continent. Because this is a virtual continent, it has room for everyone, and there are no immigration restrictions. And because there were never indigenous peoples in cyberspace, there is also no issue of taking away their land. So everyone is welcome in the free world, come to the free world, live with us in freedom. The free software movement aims for the liberation of cyberspace and everyone in it.
Source: Refactoring: Improving the Design of Existing Code, 1999, p. 33-43 as cited in: Militiadis Lytras, Patricia Ordóñez de Pablos, Ernesto Damiani (2011) Semantic Web Personalization and Context Awareness. p. 111
1990s, Why "Free Software" is better than "Open Source" (1998)
Context: While free software by any other name would give you the same freedom, it makes a big difference which name we use: different words convey different ideas.
In 1998, some of the people in the free software community began using the term "open source software" instead of "free software" to describe what they do. The term "open source" quickly became associated with a different approach, a different philosophy, different values, and even a different criterion for which licenses are acceptable. The Free Software movement and the Open Source movement are today separate movements with different views and goals, although we can and do work together on some practical projects.
The fundamental difference between the two movements is in their values, their ways of looking at the world. For the Open Source movement, the issue of whether software should be open source is a practical question, not an ethical one. As one person put it, "Open source is a development methodology; free software is a social movement." For the Open Source movement, non-free software is a suboptimal solution. For the Free Software movement, non-free software is a social problem and free software is the solution.
“The hardware world tends to move into software form at the speed of light.”
1970s, The Education of Mike McManus, TVOntario, December 28 1977
1990s, Why "Free Software" is better than "Open Source" (1998)
Context: While free software by any other name would give you the same freedom, it makes a big difference which name we use: different words convey different ideas.
In 1998, some of the people in the free software community began using the term "open source software" instead of "free software" to describe what they do. The term "open source" quickly became associated with a different approach, a different philosophy, different values, and even a different criterion for which licenses are acceptable. The Free Software movement and the Open Source movement are today separate movements with different views and goals, although we can and do work together on some practical projects.
The fundamental difference between the two movements is in their values, their ways of looking at the world. For the Open Source movement, the issue of whether software should be open source is a practical question, not an ethical one. As one person put it, "Open source is a development methodology; free software is a social movement." For the Open Source movement, non-free software is a suboptimal solution. For the Free Software movement, non-free software is a social problem and free software is the solution.
"Code + Law: An Interview with Lawrence Lessig" at O'Reilly P2P (29 January 2001)(29 January 2001)
Context: Our problem is that lawyers have taught us that there is only one kind of economic market for innovation out there and it is this kind of isolated inventor who comes up with an idea and then needs to be protected. That is a good picture of maybe what pharmaceutical industry does. It's a bad picture of what goes on, for example, in the context of software development, in particular. In the context of software development, where you have sequential and complementary developments, patents create an extraordinarily damaging influence on innovation and on the process of developing and bringing new ideas to market. So the particular mistake that lawyers have compounded is the unwillingness to discriminate among different kinds of innovation.
We really need to think quite pragmatically about whether intellectual property is helping or hurting, and if you can't show it's going to help, then there is no reason to issue this government-backed monopoly.
“Software is getting slower more rapidly than hardware becomes faster.”
In both cases the cure is simple though usually very expensive.
"Appendix II: MITE for Morons," The Odyssey File (1984), p. 123
1960s, Clarke's Three Laws, et al (1962; 1973…)
(p. 66)
Favela Digital- The other side of technology. (2013)
"Startup mines for riches in collaboration software" in The Portland Tribune (7 March 2008) http://www.portlandtribune.com/rethinking/story.php?story_id=120430910578805900
Caltech Commencement Address http://commencement.caltech.edu/archive/speakers/2012_address - 2012
Quotes https://www.wewishes.com/elon-musk-quotes/, Conversation: Elon Musk on Wired Science (2007), Foreword to Marc Kaufman's Mars Up Close: Inside the Curiosity Mission https://books.google.com/books/about/Mars_Up_Close.html?id=o6XaCwAAQBAJ&hl=en. National Geographic. ISBN 978-1-4262-1278-9.
“One way I think Erlang was a kind of software emulating Tandem machine.”
Faults, Scaling and Erlang concurrency
page 32
Making Reliable Distributed Systems in the Presence of Software Errors