I would argue - its not a comeback, it was always the "king" of web dev.
Seriously, other projects can use its success as a reference for implementation.
And I say this as a front end dev.
Seriously, other projects can use its success as a reference for implementation.
And I say this as a front end dev.
Part of it was due to the rise of SPA and Rails difficulty working with those (webpacker, anyone?), part due to poor perception of Rails 4, part due to newer options such as Elixir/Phoenix or Golang rising in popularity for backend work, part due to many of the leaders such as Yehuda Katz moving on.
Also watching from afar on HN, it seems like Rails 7 release was perceived as a sort of comeback, with quite a few articles posted in recent years praising the framework for a return to relevance.
I suspect Django and Laravel have taken a chunk of the market as like for like replacements.
Elixir/Phoenix were embraced with excitement due to Jose’s connection to the community and the ruby like syntax.
Go is good, but again I only tried it long ago and can't comment it for what it is today. I loved Ruby but I find it hard to go back to it after my experience with Elixir and Typescript. I was hoping for Crystal to go to great lengths but it doesn't seem to be the case at all.
Of course it was tongue in cheek, if the candidate is amazing yes they're a hire.
But it spoke to a reputation that Rails devs had seemingly received. I think because prior to JS/Node, it was Rails that offered newbies the fastest path into web dev.
I don't believe this is the reason for any sort of exodus, but the negative perception may be partly a reason for devs choosing other frameworks.