HP3000-L Archives

September 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Becker <[log in to unmask]>
Reply To:
Doug Becker <[log in to unmask]>
Date:
Fri, 22 Sep 2000 08:23:44 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
Legacy means old.

It also carries the connotation that we have something newer [to access the data].
Hence, any coding that is over eighteen months old, is, by definition, legacy.

The implication is that when the imbecilles who only know Windows come into power, they immediately declare anything on MPE i/X as legacy.

They write their own applications that sort of, mostly, work, and sometimes don't, which may or may not access "legacy" data.

They declare that the "legacy" platforms "are going away" for seven or eight years.

After they have to grudgingly accept the fact that the "legacy" platforms "are NOT going away",
the platforms they are working with also become legacy.

As to the question of "bilinguality": If you have a dream in the new language, you are immediately imminently qualified as bilingual.
In fact, most Colleges and Universities have considered proficiency programming languages sufficient to qualify for a foreign language.

I had my first dream in COBOL in 1972. However, Latin (a legacy language) was what qualified me for my BA.
And I never had a dream in Latin (quid pro quo).

</tongue in cheek>

ATOM RSS1 RSS2