[trs8080]

Nope, not for fun. Rather, they come from enterprise backgrounds where everything moves at a snail's pace and their methods - which they refuse to update - are wholly unsuited to a fast-moving company.

> Or is it possible that they actually know a lot of things that you don’t, and all of that “wasted time” is actually being used to provide safety, security, and proper architecture for apps?

I handle safety/security and architecture and have been for over a decade. I know what I'm doing. I would expect that any mid-large tech company in 2022 would have a way of quickly spinning up new, basic CRUD apps - if you have to write a REST API in Java from scratch over the course of two quarters every time someone needs to deploy an internal dashboard, you're doing it wrong.

> "wasted time"

Your words, not mine.

The problem in tech is a bunch of grumpy sysadmin types gatekeeping the stack and preventing people who are trying to solve business problems from doing so. Then when we introduce new technology to actually enable us to solve these problems, "oh this is a fad, I hate this language, why can't we keep things the way they were." Because you refuse to adapt, and we have stakeholders/paying customers who expect results.

[azth]

Java has nothing to do with what you described. Its modern frameworks are extremely productive and performant. Just because you might have had a bad experience with one team that moves slowly (who may very well have their reasons), does not mean that the language or ecosystem caused them to be that way.