From: no.email@nospam.invalid   
      
   dxf  writes:   
   > At no time during its writing did I consider hackers or inept users.   
   > Responsible programming was all.   
      
   Very nice.  Back in the 1980s all of us did that.  Then something called   
   the internet came along, as did computerized banking and other systems   
   which attracted highly competent malicious and/or financially motivated   
   attackers.  At that point, writing bulletproof code became not only much   
   harder, but also vitally important.  You now must ensure not only that   
   your program can do what you intended, but that it can't do what you   
   didn't intend.  Bruce Schneier[1] wrote about security engineering:   
      
       In many ways this is similar to safety engineering. ...  But safety   
       engineering involves making sure things do not fail in the presence   
       of random faults: it’s about programming Murphy’s computer, if you   
       will. Security engineering involves making sure things do not fail   
       in the presence of an intelligent and malicious adversary who forces   
       faults at precisely the worst time and in precisely the worst   
       way. Security engineering involves programming Satan’s computer.   
       And Satan’s computer is hard to test.   
      
   [1] https://www.schneier.com/essays/archives/1999/11/why_computers_are_in.html   
      
   So sure, if you're claiming that 1980s programming didn't benefit from   
   memory safe languages, maybe you're right.  Those of us who have to   
   program in the 21st century, though, need all the help we can get.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)