>>We aren't going to rewrite our legacy Java codebase in Python or something else because there is absolutely no need for it Neither would I, And if I were in

>>We aren't going to rewrite our legacy Java codebase in Python or something else because there is absolutely no need for it Neither would I, And if I were in your place I would keep Java running. And that was my whole point. Want to work on legacy stuff? Or the newer and better projects? By the way, Python isn't that new these days either. Start up's I know of are going the Go, Clojure and Scala way. >>when you're running the company, you have to consider things from a business perspective rather than a technical one. Which is why for the new projects it makes sense to chose the latest tools which have little tech debt, which have fixed problems with older tools and will hang on for longer time. >> people do nothing but sip the Java haterade without realizing what it is good for. I don't debate that at all. But frankly speaking Java being good doesn't mean there are better things than that. >>Honestly I couldn't care less- I'm not trying to change your way of thinking Neither am I, I have seen first hand what happens when you stick to legacy tools. The jobs dry out, the projects you can work on move towards legacy end and lastly your career as a large suffers. >>but in case some other aspiring dev is reading this, I'd strongly suggest to not be close-minded about powerful tools like Java that have mature ecosystems and an excellent community around them. If a young dev is reading this, please treat tools as tools and have to special attachment to them. Learn to adapt and move on to newer things as and when necessary.