From your linked blog post: > The situation is particularly ironic because the argument that has been advanced for discarding Lisp in favor of C++ (and now for

From your linked blog post: > The situation is particularly ironic because the argument that has been advanced for discarding Lisp in favor of C++ (and now for Java) is that JPL should use "industry best practice." The problem with this argument is twofold: first, we're confusing best practice with standard practice. The two are not the same. And second, we're assuming that best (or even standard) practice is an invariant with respect to the task, that the best way to write a word processor is also the best way to write a spacecacraft control system. It isn't. Well said. I think I'm going to have to hold onto this argument for a rainy day.