You make a good point, although I was exclusively referring to front-end JS frameworks. Of course you'd want to update Spring, .NET and whatever else you're usi

You make a good point, although I was exclusively referring to front-end JS frameworks. Of course you'd want to update Spring, .NET and whatever else you're using due to vulnerabilities. But to the point you were making - it's not impossible that browsers could evolve to the point where our current version of React is unusable and it's been long relegated to the buzzword graveyard. Of course in that situation we'd have to maintain our own React branch or rewrite in whatever was a popular front-end framework at the time. My point is that getting stressed out about the front-end JS framework churn isn't helpful to anyone. Pick a stack and stick with it, and only move when it's simply not productive to stay.