> Posts like this are almost something to be ashamed of “we rewrote an entire subsystem because we wanted to use a language we like”. That’s really failing in y

> Posts like this are almost something to be ashamed of “we rewrote an entire subsystem because we wanted to use a language we like”. That’s really failing in your responsibility to the company. I would tend to agree. I don't understand these sorts of decisions to rewrite huge sites in niche languages and frameworks. You tend to get one engineer who really likes some language, has some clout, and is able to pitch it as a good idea. And then the blog posts about how it saves the company untold millions, while hiding all of the associated costs. Not only is it niche, so your costs going forward will be higher, it even required investing in new "tools and strategies" just to bechmark it. "Elixir has proven so efficient that testing the limits of our services became a challenge unto itself, requiring investment in new benchmarking tools and strategies". I wouldn't personally gamble on a robust job market for Elixir developers in a decade. And those there are will be able to command higher wages. Sure, they will be out there. But so were COBOL developers for Y2K.