3 ms·
It's a generational thing as well. New programmers adopt whatever is fashionable when they start out and move on from there. Ten years ago that would be Ruby an
by jillesvangurp 7y ago
It's a generational thing as well. New programmers adopt whatever is fashionable when they start out and move on from there. Ten years ago that would be Ruby and quite a few Ruby developers ended up in e.g. the Elixir and Rust communities. Five years ago that would have been Javascript. Today that would be Typescript and lots of Javascript developers would have progressed to that naturally (as well as Go, Rust, and a few other languages).
This is significant because the number of programmers world wide doubles every five years (https://blog.cleancoder.com/uncle-bob/2014/06/20/MyLawn.html https://blog.cleancoder.com/uncle-bob/2014/06/20/MyLawn.html). So whomever was doing perl 20-25 years ago is outnumbered 16-32 x by everyone else in the business before you even consider the vast numbers of former perl developers that threw in the towel a long time ago. This means most new projects will bias to whatever skills are available cheaply (i.e. whatever is popular) and many of the relatively few older developers end up adapting to that.
I actually know a couple of companies with some active perl code bases. Wouldn't touch it myself since I was an early Java adopter (now using Kotlin) but they seem to manage. Though I imagine finding more developers is going to be tough. Languages never die but they do tend to become shadows of their former glory. I don't think anyone would suggest using Cobol for a new project at this point in time. It's been considered a legacy language for as long as I've been programming (since the late eighties). It's dead as door nail; never coming back. But you can still make good money maintaining code written nearly half a century ago.