
For survivors, languages designed to solve specific problems have enjoyed a long life. Fortran was designed by John Backus to facilitate converting formulas to machine language (formula translator), Basic came out of Dartmouth to make teaching programming easy, B came from Ken Thompson at Bell Labs which led to Dennis Richie's C in order to overcome obstacles with the Multics/PL-1 project. More recently, Perl, PHP etc - also were driven by individuals solving specific problems.
What fell? PL/1, designed by IBM to combine the utility of Cobol and Fortran failed. The Defense Department jumped in and designed ADA and so on until we arrive at Java. Designed by Sun - again, not a response to a specific issue but rather a coporate strategy to solve classes of perceived problems.
Bottom line - programming/scripting languages, designed by individuals to solve individual problems seem to enjoy a longer life than languages designed by corporate groups that address large classes of problems (to increase market share?).
And another point - typically languages initiated by individuals have a shallow learning curve (remember printf("Hello world");) whereas languages initiated by groups tend to be too feature-rich (look at PL/1). The remarkable lesson for me is how a few individuals addressed their own problems in such a way that the resulting language could be extended while maintaining a very shallow learning curve.
"I'm not a god, I was misquoted." -- Lister, Red Dwarf