You don’t actually have to setup your web-development environment like the hype dictates. I mean, work in a Danish municipality with more than 5k employees and 60k citizens who directly use our, mainly web-based, solutions daily. We build around 50 a year, and maintain a few hundred of them, and almost none of them are build with a JavaScript MVVM framework.

Not because Vue/React/Angular aren’t nice, but because we don’t have to. If it doesn’t need to run offline, then a MVC framework with Ajax will do just fine, and they are extremely productive. Both because errors are server side, but also because asp mvc hasn’t really seen radical changes for almost a decade. We also rarely put things in containers, we don’t do automated CI/CD and we certainly don’t orchestrate things with Kubernetes. Not that there is anything wrong with doing that, but we’re not Netflix, we can publish a new build directly to an IIS during a slow period and no one will notice the service being gone for 5 seconds.

Sometimes I think it pays to do a little JOMO instead of all that FOMO. Especially if you don’t want to burn out. Changes are a constant in our business, but you need to make absolutely certain that adopting those changes make sense, and it has to make sense in the real world, not on hacker news. Our business doesn’t care one bit about the front-end tech stack, as long as it performs like they want it could be written in ASP webforms.