asciilifeform: e.g., 'let's use square brackets for certain lists'
asciilifeform: mod6: similar to the old 'armed bear common lisp', except that it was written by a 'clever tricks' crackpot who added in ten truckloads of homegrown ustard idiocy
asciilifeform: mod6: some years ago, i attended a few meetings of a local clojurist society. ended up barfing and writing article, http://www.loper-os.org/?p=42 (and sequel, http://www.loper-os.org/?p=374 ) that ~still~ get flamez, and - until recently - were among the top google results for subj...
asciilifeform: mircea_popescu: in usa software cos were EXEMPTED from liability suits
asciilifeform: or functional requirements, poor design, or programming mistakes. The root cause of the hazards will be exposure of implementation-defined behaviors in a programming language. Who will the lawyers sue over the consequences of those hazards?'
asciilifeform: the new hardware will be received as a complete surprise by most users of the upgraded system and by their management. The surprise may be accompanied by hazardous events because of incorrect control of a safety critical system. People may be injured or die, the environment may be seriously damaged, and very expensive systems may be damaged or destroyed. The root cause of the hazards will not be po
asciilifeform: 'As a software safety engineer I find the implementation-defined aspects of C++ bit-fields to be very unsettling. A project may verify that its C++ bit-fields work as intended on a particular architecture, but when a technology refresh is performed in several years, there is no assurance that the C++ program will continue to work properly on the new hardware. The failure of the C++ program to run on
