> If the switch away from ... a newer language and eco-system allows you to achieve massive scale with less technologies and less moving parts, then you absolut

> If the switch away from ... a newer language and eco-system allows you to achieve massive scale with less technologies and less moving parts, then you absolutely have a professional obligation to do so. Read this again. It make total sense. Eventually, some path become running against the current, and then the better path is move to something else. And what about that millons-of-lines of code? Is the same thing as "what about all the investment in money with that inneficient car that eat gasoline like is not a tomorrow, I push so much on it but the new tech is far more efficient?, and you tell me, let that in the past?" Yes. You put that millons-of-lines in the past and rebuild. If you have the correct mindset the change will pay off GREATLY... P.D: I do this for work several times in my life, With very drastic/radical changes. In fact, the MORE RADICAL the BEST. "Small" changes are not worth it. The $$$ is not there. But when you do a hard change is when the benefits get more evident...