If there are no security problems affecting your project, and you don't benefit from new features, there is no urge to update. And even then, it's a cost/benefi

If there are no security problems affecting your project, and you don't benefit from new features, there is no urge to update. And even then, it's a cost/benefit ratio. Updating is a constraint, one you follow either because it solves a problem or avoid a pitfall, not a goal. I migrated most of my stuff to Python 3 years ago, but for some of my clients, despite that 2.7 is not supported anymore, I advice to just download a copy of everything they need offline as a safety measure and keep the system running as-is forever. Raw HTML + jQuery + Django 1.x + VPS still deliver fine. Just because I can do react + microservices does not mean it should be a default response. There are servers running barely touched from one or two decades ago and they do their job perfectly. So yes, some client side libs are going to be there for years and years. If the UI works, it's alright. Software is not an end, it's a tool. Being passionate about it, it's easy to forget that, but we use software to help the real world, not the other way around. Not saying of course you should never update nor use modern technology when appropriate: technical debt must be paid. But it's important to recognize when you need to do it, and when you just want a shiny toy or to look good.