Considered harmful

Considered harmful is a part of a phrasal template used in the titles of at least 65 critical essays in computer science and related disciplines. [1] Its use in this context originated in 1968 with Edsger Dijkstra’s “Go To Statement Considered Harmful”.

History

Considered harmful was popularized by Edsger Dijkstra’s “Go To Statement Considered Harmful”, [2] [3] published in the March 1968 Communications of the ACM (CACM), in which he criticized the excessive use of the GOTO statement in programming. languages of the day and advocated structured programming instead. [4] The original title of the letter, as submitted to CACM, was “A Case Against the Goto Statement”, but CACM editor Niklaus Wirth haschanged the title to “Go To Statement Considered Harmful”. [5] Regarding this new title, Donald Knuththat ” Dr. Goto cheerfully complained that he was always being eliminated.” [6]

Frank Rubin published a review of Dijkstra’s letter in the March 1987 CACM where it appeared under the title “GOTO Considered Harmful ‘Considered Harmful”. [7] The May 1987 CACM printed further replies, both for and against, under the title “GOTO Considered Harmful” Considered Harmful “Considered Harmful?”. [8] Dijkstra’s own response to this controversy was titled Somewhat Disappointing Correspondence . [9]

Considered harmful was already a journalistic cliche used in the headlines, well before the Dijkstra article, as in, for example, the headline over a letter published in 1949 in The New York Times : “Rent Control Controversy / Enacting Now of Hasty Legislation Considered Harmful” . [10]

Related essays

  • William Wulf and Mary Shaw (February 1973). “Global Variable Considered Harmful”. ACM SIGPLAN Notices . 8 (2): 28-34. doi : 10.1145 / 953353.953355 .
  • Bruce A. Martin (November 15-19, 1976). “Letter O Considered Harmful”. proposal considered by X3J3 members . Brookhaven National Laboratory, Upton, NY: X3J3: ANSI Fortran Standards Committee. (Full proposal text was included in post-meeting distribution; see summary .)
  • Rob Pike and Brian Kernighan (1983). “UNIX Style, Golden Cat -v Considered Harmful” . USENIX .
  • John McCarthy (December 1989). “Networks Considered Harmful for Electronic Mail” . CACM . 32 (12): 1389-1390.
  • CA Kent; JC Mogul (January 1995). “Considered Harmful Fragmentation” . ACM SIGCOMM Computer Communication Review . 25 : 75-87. doi : 10.1145 / 205447.205456 .
  • Tom Christiansen (October 1996). “Csh Programming Considered Harmful” . See C shell .
  • Peter Miller (1998). “Recursive Make Considered Harmful” . AUUGN . 19 (1): 14-25. Archived from the original on 2015-03-30.
  • Jonathan Amsterdam (February 2002). “Java’s New Considered Harmful” . Software Development Magazine .
  • Ian Hickson (September 2002). “Sending XHTML as text / html Considered Harmful” .
  • Eric A. Meyer (December 2002). ” ” Considered Harmful “Considered Harmful Essays” .
  • C. Ponder; B. Bush (1992). “Polymorphism considered harmful”. ACM SIGPLAN Notices . 27 (6): 76-79. doi : 10.1145 / 130981.130991 .
  • J Yoon; Mr. Liu; B Noble (April 2003). “Random Waypoint Considered Harmful” . Infocom . 2 : 1312. doi : 10.1109 / INFCOM.2003.1208967 .
  • At Mishra; V Shrivastava; S Banerjee; W Arbaugh (June 2006). “Partially Overlapped Channels Not Considered Harmful” . Sigmetrics . 34 : 63. doi : 10.1145 / 1140103.1140286 .
  • Alexander Sotirov; Marc Stevens; Jacob Appelbaum; Arjen Lenstra; David Molnar; Dag Arne Osvik; Weger Tipper (December 2008). “MD5 considered harmful today – Creating a CA certificate” .
  • Jun-ichiro itojun Hagino (October 2003). “IPv4-Mapped Addresses on the Wire Considered Harmful” .
  • Rich Felker (aka ‘dalias’) (July 2013). “NULL considered harmful” . See C_ (programming_language) .
  • Paul Ceruzzi (June 2015). “Star Trek Considered Harmful” .
  • Howard Chu (February 2008). “GnuTLS Considered Harmful” .
  • Joanna Rutkowska (October 2015). “Intel x86 considered harmful” (PDF) .

See also

  • snowclone

References

  1. Jump up^ “Miscellaneous – Considered Harmful” . Archived from the original on 2009-05-03 . Retrieved August 17, 2009 .
  2. Jump up^ Edsger Dijkstra (March 1968). “Go To Statement Considered Harmful”. Communications of the ACM (PDF) . 11 (3): 147-148. doi : 10.1145 / 362929.362947 . The unbridled use of the go to statement has become an immediate consequence that it becomes terribly hard to find a meaningful set of coordinates in which to describe the process progress. … The go to statement is it too primitive, it is too much an invitation to make a mess of one’s program.
  3. Jump up^ Dijkstra, Edsger W. EWD-215 (PDF) . EW Dijkstra Archive. Center for American History, University of Texas at Austin . (transcription)
  4. Jump up^ David R. Tribble (February 2005). “Go To Statement Considered Harmful: A Retrospective” .
  5. Jump up^ Dijkstra, Edsger W. What led to “Notes on Structured Programming” (EWD-1308) (PDF) . EW Dijkstra Archive. Center for American History, University of Texas at Austin . (transcription) (June, 2001)
  6. Jump up^ Kanada, Yasumasa (2005), “Events and Sightings: An obituary of Eiichi Goto”, IEEE Annals of the History of Computing , 27 (3): 92, doi : 10.1109 / MAHC.2005.37
  7. Jump up^ Frank Rubin (March 1987). ” ” GOTO Considered Harmful “Considered Harmful” (PDF) . Communications of the ACM . 30 (3): 195-196. doi : 10.1145 / 214748.315722 . Archived from the original (PDF) on March 20, 2009.
  8. Jump up^ Donald Moore; Chuck Musciano; Michael J. Liebhaber; Steven F. Lott; Lee Starr (May 1987). ” ” ‘GOTO Considered Harmful’ Considered Harmful ‘Considered Harmful?’ (PDF) . Communications of the ACM . 30 (5): 351-355. doi : 10.1145 / 22899.315729 .
  9. Jump up^ Dijkstra, Edsger W. Somewhat Disappointing Correspondence (EWD-1009) (PDF) . EW Dijkstra Archive. Center for American History, University of Texas at Austin . (transcription) (May, 1987)
  10. Jump up^ Mark Liberman (April 8, 2008). “Language Log: Considered harmful” . Retrieved August 17, 2009 .

Leave a Reply

Your email address will not be published. Required fields are marked *

Copyright computerforum.eu 2018
Shale theme by Siteturner