Bug 259708 lists four "Lessons" learned (hopefully). May I suggest a fifth lesson (or "Bug handling Bug"), Lesson Number Zero: Shift the software "best practices" paradigm from Debugging to Preventing bugs.

This software best practices paradigm shift also means a paradigm shift in software tools, including the choice of computer language. One example: SPARK, a "strict subset" of ADA95, Proof More Cost-Effective Than Testing? (18 page PDF slide show presentation), used for the C-130J Super Hercules and C-27J Spartan freight aircraft and other mission critical software applications.

Question1: Does such a "strict subset" of C, C++, C#, D, FORTRAN, PERL, Postscript/Ghostscript, PHP, Python, Ruby, etc., etc., exist?

Question2: Are open-source developers prepared to change their software best practices paradigm from Debugging to Preventing bugs?

Question3: Are open-source developers prepared to change their choice of software languages to "strict subsets" such as SPARK?

Thank you,
Eddie Maddox