Since this article is about when to upgrade depending on your language, I'd like to know if there is a place with information about languages/ecosystems by "lon

Since this article is about when to upgrade depending on your language, I'd like to know if there is a place with information about languages/ecosystems by "longevity", which could be time before you have to upgrade your language, time before you have to upgrade your packages, or something like that. Of course this would be a complex measure. For example, having to upgrade the language AND change code would be worse than having to upgrade the language and don't change code. Same thing for dependencies. For example, Go has strong backwards compatibility guarantees, but the last supported versions is less than a year old (1.16.9). PHP's security support of 7.3 ends in a bit more than a month, for a total of 3 years of support. Node.js is a bit younger but will still have 3 years of support. Java 8 still has extended support until 2030 by Oracle. There are also things like, with PHP, you may just have to change the environment, but with Go, you would have to recompile the code. Maybe this could be better expressed as a "maintenance cost" or "churn"? I often hear that "ecosystem X has a lot of churn", but often it's not really well justified. For example, frontend JS moves a lot, but backend JS seem to have been "stuck" on Express for quite some time, and Express itself seems stable, if a bit dated. Maybe that's because we only hear about people changing code, frameworks, best practices? I don't see a lot of articles like "my 5 years old codebase is pretty much the same as when I began", compared to "I switched from X to Y".