Re: yeesh Can we have some more @#$% willy wagging please?
" If you aren't prepared to use the right tool, instead of what makes your stiffy bits stand up, you are a problem."
I'd replace "right tool" with "most appropriate tool" since in business it's often necessary to compromise. Many Mainframe solutions are still in play because replacing them would cost more than keeping them, yet in many instances they are not the right tool any more.
Throwing away a code base because a developer says that <insert language de jour here> is the right tool isn't necessarily a wise choice either. Firstly, does more than one developer in the team think that? Has said developer been saying that for more than a week, or was he screaming about containers last week? How much do developers with <new skill> cost compared to <old skill> and how many of them are there. There are a lot of Java skills and a lot of cheap Java labour so ditching your code base in Java might not be the best business plan. In fact, it would likely have to go on the company risk register since it's such a massive change, and that might affect the cost of borrowing...
Biting the hand that feeds IT
