Prowling The Ruins Of Ancient Software

from the from-an-archaeological-perspective dept

The issue of preserving obsolete software seems to come up around here every six months or so. However, this latest article, from Salon, looks at it from a slightly different perspective. Most articles talk mainly about the need to set up systems that will easily let people access old data. This piece, though, looks at it more from an archaeological perspective, talking about the importance of preserving the code itself - rather than preserving the code for the sake of being able to access data. Lots of people seem to have an interest in saving the code, but the biggest hurdle is the ever-friendly DMCA that prevents people from saving most proprietary code.
Hide this

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.

Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.

While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team


Reader Comments

Subscribe: RSS

View by: Time | Thread


  1. identicon
    Anonymous Coward, 30 Jul 2003 @ 12:35am

    Mmmm 1980s code

    The kind that valued execution speed at all costs, at the cost of readability or maintainability? Depending on the programmer you asked, a "good" programmer never inserts comments in his code, because it might sacrifice the speed, or that those who cannot figure out comment-less code do not deserve to program.

    How about them 999 return codes?

    link to this | view in thread ]

  2. identicon
    thecaptain, 30 Jul 2003 @ 10:34am

    Re: Mmmm 1980s code

    How the h*ll would comments in the code sacrifice speed?

    Mind you I didn't use compilers in the 80s but didn't they then as now simply ignore code comments when compiling?

    link to this | view in thread ]

  3. identicon
    Anonymous Coward, 30 Jul 2003 @ 12:32pm

    Re: Mmmm 1980s code

    Interpretive languages were common back then, when C was still a new language. Also, when programmer did not have access to the internet back then, there were urban legends that comments do slow down compilers.

    link to this | view in thread ]


Follow Techdirt
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Discord

The latest chatter on the Techdirt Insider Discord channel...

Loading...
Recent Stories

This site, like most other sites on the web, uses cookies. For more information, see our privacy policy. Got it
Close

Email This

This feature is only available to registered users. Register or sign in to use it.