2010 - Making switch from PHP to Ruby
2013 - Making switch from Ruby to Node
2016 - Making switch from Node to Go
2019 - Making switch from Go to {hype}
2013 - Making switch from Ruby to Node
2016 - Making switch from Node to Go
2019 - Making switch from Go to {hype}
Of course, it's good to be skeptical of the current hyped flavor of the moment. But some languages really are better than others for specific tasks, and new languages do sometimes improve on their predecessors.
I make it a rule to only jump on the new bandwagon when I know it's not going to explode in 3 months and currently isn't on fire.
2019 - switch to PL/1 and raw disk sector addressing because bigdata smoothie silicon googley disrupt the world
I've seen this very recently personally, where I was accused of adopting hype for switching to Swift for a major rewrite of my app, where I'd pretty much start over in Objective-c anyways so I may just as well do it in a safer, much nicer language that's going to be the future of the platform eventually anyway...
It turns out that you don't have to switch - if your current stack works well for you stick with it. It doesn't make you "less cool". But it also doesn't mean that somebody else doesn't have a legitimate reason to adopt the new technology, and this is a pretty textbook example of what I'd call a justified switch.