The Long Life of Open Source Code

Doghouse – Code Longevity

Article from Issue 247/2021
Author(s):

As two examples of how open source code can evolve, maddog discusses the long history of text editors and of the RAND message handling system.

Recently I was discussing with friends how long certain pieces of code have lasted … perhaps not exactly the same piece of code, but a recognizable version of the original that has continued to evolve.

One example of this is the simple text editor.

When I started programming, I used 80-column punched cards and the Fortran language. If you made a mistake, you could stick the bad card into a particular slot on the card punch, duplicate the correct part of the card, and then continue typing to complete the statement. It was horrible, but it was all we had.

[...]

Use Express-Checkout link below to read the full article (PDF).

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

SINGLE ISSUES
 
SUBSCRIPTIONS
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • A tale of long-lived Free and Open Source projects

    I was reading an Atlanta Linux Enthusiasts (ALE) mailing list recently that has been around a long time. Many of the people on that list have been reading and writing to the list for 20 years. One of them had just installed a version of the Common Desktop Environment (CDE), which was developed when I was working at Digital Equipment Corporation (DEC) more than 20 years ago.

  • maddog's Doghouse

    There are many FOSS databases available inexpensively today, and they might serve new projects well.

  • Doghouse – Problem Solving

    How you approach a problem goes a long way toward success in code development.

  • maddog's Doghouse

    The efficiency alone of a programming language doesn't show the full picture.

  • Doghouse: Taking the Initiative

    "maddog" describes how forging your own path can sometimes lead to better results than simply following instructions.

comments powered by Disqus