3 ms·
If I'm at JPL, doing C++, they probably have several more C++ programmers. I probably work with some of them. If I'm gone, they probably have someone who can
by AnimalMuppet 7y ago
If I'm at JPL, doing C++, they probably have several more C++ programmers. I probably work with some of them. If I'm gone, they probably have someone who can take over, people who maybe use the same coding standard I use (they almost certainly have one for C++). But if I'm the first person there using Lisp, there probably isn't a standard (unless I wrote it, and if so, it's a standard nobody else there uses). There may not be anyone else there who knows the language. So while Lisp may be a perfectly reasonable language in terms of functionality, it's not a perfectly reasonable language in terms of the organizational issues. I, the programmer who wants to use Lisp, may not have to think about those issues, but managers do.
- Twisol 7y agoYes, I agree! I merely think you overvalue C++ in this case. There's lots of C/C++ code that most people can't understand either -- and not for lack of knowing the language. Apropos of nothing, I found Peter Naur's "Programming as Theory Building" [1] an enjoyable read on the topic of maintaining software after the original developers depart. [1] http://pages.cs.wisc.edu/~remzi/Naur.pdf http://pages.cs.wisc.edu/~remzi/Naur.pdf
- p_l 7y agoNote that JPL had many people using Lisp - in fact, it was C++ that was relative newcomer.