It could be anything in the top 20, really [0]. The problem is that devs have an impulse to do something experimental and cool, since they have to work with wor

It could be anything in the top 20, really [0]. The problem is that devs have an impulse to do something experimental and cool, since they have to work with workhorse languages all day at their day jobs. The myth that they tell themselves is that $REVOLUTIONARY_FEATURE_Y will greatly improve their productivity, but the fact of the matter is usually that no matter how revolutionary the features, it's hard to overcome the benefits that come from an active ecosystem of well-tested and widely used libraries. Even if productivity is improved 20x by the revolutionary feature, a library that has 10 man-years of effort in it will take you 6 months to implement. Rinse and repeat. This is not to mention the availability of online references and established conventions/best practices, the impact of hitting esoteric errors, and so on. A good example of this is probably reddit. Originally written in Lisp, they eventually gave up and compromised down to Python due to improved tooling and library availability. [1] [0] https://www.tiobe.com/tiobe-index/ https://www.tiobe.com/tiobe-index/ [1] https://redditblog.com/2005/12/05/on-lisp/ https://redditblog.com/2005/12/05/on-lisp/