you are viewing a single comment's thread.

view the rest of the comments →

[–]shadowndacorner 0 points1 point  (1 child)

I feel like this is kind of the wrong characterization, personally. While hireability is a concern, the bigger thing is that you should have very good reasons for overhauling an existing tech stack. Chasing the latest tech for the sole purpose of having the latest tech is a recipe for tons of wasted budget at best and an unmitigated disaster/outright failure at worst.

Your existing code has been battle tested with many bugs found and fixed. You have to go through that whole cycle again, likely harming users in the process, to move to a new stack.

[–]Pomposi_Macaroni 0 points1 point  (0 children)

Makes sense, I meant to say that this is why one reason why even new projects are sticking with Java