|
||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||
Warning: The download time has expired please click on the item to try again. ABSTRACT
New programming languages are born every day. Why do some succeed and some fail? In 50 years, weve already seen numerous programming systems come and (mostly) go, although some have remained a long time and will probably do so for: decades? centuries? millennia? The questions about language designs, levels of abstraction, libraries, and resulting longevity are numerous. Why do new languages arise? Why is it sometimes easier to write new software than to adapt old software that works? How many different levels of languages make sense? Why do some languages last in the face of "better" ones? REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
REVIEW
"Manuel E. Bermudez : Reviewer"
Mashey speculates on the reasons for the success of some programming languages, and the failure of others. After some initial speculation about the role of "programmer archaeologists" in the distant future, he describes various levels of programmi
more...
|
||||||||||||||||||||||||||||||||||||||||