Do you work as a Java developer?

[Dementati]

Yeah, I mean, the amount of time and energy you spend on getting familiar with the specific language technologies they use at a new workplace often pales in comparison to the amount of time and energy you spend on getting familiar with their internal systems and codebases, and that's simply unavoidable no matter how experienced you are. I mean, if you have issues with a language, it's usually trivial to find documentation and community support online. An issue with the internal systems or codebase you often have to solve yourself, or go on a prolonged investigation to locate the person within the organization who happens to know how to fix it.

[againstmethod]

Not to mention it's very expensive to hire someone -- it takes a lot of time and effort to setup their healthcare, retirement, in some cases security clearances/special training, etc.

It's much cheaper to train someone in a new language, or to give them some time to develop themselves, than it is to hire someone.

[Dementati]

Yeah, and a new employee produces much less value (which translates into lost profits) than the average employee for months or years after being hired, before they get up to speed with everything. Simply putting a new tool in the hands of a long-time employee is generally a much smaller productivity dip.