“Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. Basically, a lot of the problems that computing has had in the last 25 years comes from systems where the designers were trying to fix some short-term thing and didn’t think about whether the idea would scale if it were adopted. There should be a half-life on software so old software just melts away over 10 or 15 years.”

—  Alan Kay

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

Adopted from Wikiquote. Last update Sept. 14, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. Basically…" by Alan Kay?
Alan Kay photo
Alan Kay 25
computer scientist 1940

Related quotes

Richard Stallman photo

“The term "free software" has an ambiguity problem: an unintended meaning, "Software you can get for zero price," fits the term just as well as the intended meaning, "software which gives the user certain freedoms."”

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

We address this problem by publishing a more precise definition of free software, but this is not a perfect solution; it cannot completely eliminate the problem. An unambiguously correct term would be better, if it didn't have other problems.
1990s, Why "Free Software" is better than "Open Source" (1998)

Robert T. Kiyosaki quote: “A job is only a short-term solution to a long-term problem.”
Robert T. Kiyosaki photo

“A job is only a short-term solution to a long-term problem.”

Robert T. Kiyosaki (1947) American finance author , investor

Rich Dad Poor Dad: What the Rich Teach Their Kids About Money-That the Poor and the Middle Class Do Not!

Barry Boehm photo

“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

“The fate of the soil system depends on society's willingness to intervene in the market place, and to forego some of the short-term benefits that accrue from 'mining' the soil so that soil quality and fertility can be maintained over the longer term.”

Eugene P. Odum (1913–2002) mathematician, ecologist, natural philosopher, and systems ecologist

Eugene Odum (1993) Ecology and our endangered life-support systems. p. 143

Lawrence Lessig photo

“The current term of protection for software is the life of an author plus 70 years, or, if it's work-for-hire, a total of 95 years. This is a bastardization of the Constitution's requirement that copyright be for "limited times." By the time Apple's Macintosh operating system finally falls into the public domain, there will be no machine that could possibly run it. The term of copyright for software is effectively unlimited.”

Lawrence Lessig (1961) American academic, political activist.

May the Source Be With You (2001)

“When software applications became larger and larger, people such as Shaw and Garlan coined the term software architecture. This notion of architecture deals with the key design principles underlying software artefacts. In the 1980s and 1990s, people became aware that the development of information technology (IT) should be done in conjunction with the development of the context in which it was used. This led to the identification of the so-called business/IT alignment problem. Solving the business/IT alignment problem requires enterprises to align human, organizational, informational, and technological aspects of systems. Quite early on, the term architecture was also introduced as a means to further alignment, and thus analyzes and solves business? IT alignment problems, Recently, the awareness emerged that alignment between business an IT is not enough, there are many more aspects in the enterprise in need of alignment. This has led to the use of the term architecture at the enterprise level: enterprise architecture.”

Erik Proper (1967) Dutch computer scientist

Martin Op 't Land, Erik Proper (2009) Enterprise Architecture: Creating Value by Informed Governance. p. 26-27

“In a city where buzzwords and catch phrases have a half-life of perhaps six months to a year, the term and the concept of "competitiveness" have lasted much longer; there is every sign we'll hear it for many years to come.”

Allen B. Rosenstein (1920–2018) American systems engineers

Allen B. Rosenstein and Phillip Burgess (1988) "U.S. Competitiveness." Bureaucrat. Vol. 17-18. p. 21.

A. Wayne Wymore photo

“The problem of the design of a system must be stated strictly in terms of its requirements, not in terms of a solution or a class of solutions.”

A. Wayne Wymore (1927–2011) American mathematician

A Wayne. Wymore (2004) " The nature of research in systems engineering http://sse.stevens.edu/fileadmin/cser/2004/papers/211-Paper119.pdf"; As cited in: Eric David Smith (2006) Tradeoff Studies and Cognitive Biases. p. 31.

Lawrence Lessig photo

“I would dramatically reduce the safeguards for software — from the ordinary term of 95 years to an initial term of 5 years, renewable once. And I would extend that government-backed protection only if the author submitted a duplicate of the source code to be held in escrow while the work was protected. Once the copyright expired, that escrowed version would be publicly available from the copyright office.
Most programmers should like this change. No code lives for 10 years, and getting access to the source code of even orphaned software projects would benefit all. More important, it would unlock the knowledge built into this protected code for others to build upon as they see fit. Software would thus be like every other creative work — open for others to see and to learn from.”

Lawrence Lessig (1961) American academic, political activist.

May the Source Be With You (2001)

Theodore Kaczynski photo

“In the short term, natural selection favors self-propagating systems that pursue their own short-term advantage with little or no regard for long-term consequences.”

Theodore Kaczynski (1942) American domestic terrorist, mathematician and anarchist

Source: Anti-Tech Revolution: Why and How (2015), p. 44

Related topics