From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_05,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f948976d12c7ee33 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-27 09:21:36 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-pas-nf2!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!stamper.news.atl.earthlink.net!harp.news.atl.earthlink.net!not-for-mail From: Richard Riehle Newsgroups: comp.lang.ada Subject: Re: Boeing and Dreamliner Date: Fri, 27 Jun 2003 09:24:34 -0700 Organization: AdaWorks Software Engineering Message-ID: <3EFC6FC2.B96DAEA4@adaworks.com> References: Reply-To: richard@adaworks.com NNTP-Posting-Host: 3f.bb.a0.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Server-Date: 27 Jun 2003 16:23:12 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en Xref: archiver1.google.com comp.lang.ada:39825 Date: 2003-06-27T16:23:12+00:00 List-Id: Hyman Rosen wrote: > rleif wrote: > > All the Boeing management need to do is read the JAVA and C# literature on > > why these languages were created. Choosing an inferior technology is bad; > > choosing and inferior, obsolete technology is worse. > > > > I might note that there are enough potential expert witnesses in this group > > to cause Boeing grave financial damage in the event management is negligent > > in the choice of programming language and this negligence leads to deaths or > > injuries. > > Ada made the Ariane 5 crash! Untrue. Engineering mismanagement made Ariane 5 crash. The Ada code that caused a problem in Ariane 5 was perfectly good code reused from Ariane 4. It worked exactly as intended on Ariane 4. The launch characteristics of Ariane 5 were different from Ariane 4, and this difference was overlooked by the engineering team. To use an analogy, this is much like prescribing a medicine for a patient that works exactly as intended on most patients. However, some patients will be allergic to that same medicine. The physician has a responsibility to do a careful medical analysis to ensure there are no contra-indicated circumstances in the health history or the targeted patient. The engineer must determine whether there are differences between the targeted platforms for existing, albeit otherwise correct, software components. Richard Riehle