Old Code Gets Younger Every Year
&gt; The real horsemen of the legacy apocalypse is the depth of the dependency tree.<p>I won&#x27;t speak for Java or Python. For Node&#x2F;JS, I do not see this being a problem for the future. The reason is because npm is so fragile that the entire thing falls over <i>today</i> if you just look at it wrong. The very second you run &quot;npm install&quot; you have a mountain of instant tech debt. The primary reason for this is because the people writing JavaScript do not know what they are doing. They have not cut their teeth on libraries in C&#x2F;C++ or other languages and have no clue how backwards compatibility or versioning works. If you doubt what I&#x27;m saying, then I invite you to do your own quality inspection of any major JS library or framework out there. I&#x27;m not going to name names, but the vast majority of it is pure shit.<p>In my experience, JS code has a life expectancy of about a year and a half. Give or take. After that, it is rewritten. Which also contributes to the lack of quality in the JS ecosystem. There is a built-in assumption that this code won&#x27;t survive past the time your average dev gets bored of it.<p>People, today, do not realize there are JS frameworks that predate React&#x2F;Angular&#x2F;etc. and <i>have already died</i>. Once popular frameworks. And I&#x27;m not talking jQuery. You don&#x27;t see them because JS development = churn. You don&#x27;t even see CoffeeScript mentioned today, and that was just a few years ago.