Node 12? Holy s** that is only 4 years old. Meanwhile in the real world most applications are running on 10+ year old stacks - Java 8, Python 2, Angular.js etc etc
And don't get me started on the Cold Fusion code I wrote in 1997 that probably still is buried somewhere in the Epic software that generates mycharts for HIPAA compliant doctor/patient reporting. Last year I was almost arrested for hacking when my real name triggered a security flag that I might be doing something evil when I really just needed a colonoscopy.
Think the internet is forever? Try being scowled at for innocent code you wrote as a kid.
And stay off my lawn...
I think what kills me most is when you encounter these codebases in the real world and you're like "wait … this entire startup is younger than Python 3 significantly", and younger than the point where there was good support from the ecosystem…
Double bonus points these days if younger than the Python 2 deprecation date…
(And yet every security team lists some variant of "keeping stuff updated" in their process docs, somehow.)
Source: trust me, bro
Source: trust me, bro
The earth is round.
Source: trust me, bro
Source: trust me, bro
If you work at tech companies led by tech people who think of their companies as tech companies, yah, you'll probably be on new(ish) versions.
Most software isn't written at companies like that; it's written at boring business companies (like banks and utilities) that are led by business people who say "what do you mean to want to update java? Isn't it working fine? That would cost us a huge amount of money and be super risky and it's not even end-of-life. Go write more Java 8."
> "... it's not even end-of-life. Go write more Java 8."
Sounds like Oracle is enabling this response by not EOL'ing it. Just like IE didn't die completely until Microsoft stopped supporting it.