1. Rails isn't cool.
2. If you spend enough time hunting around, you can find Node libraries that, collectively, do everything Rails does out of the box.
3. Node is "cool."
4. A third party product which has nothing to do with Rails for building native iOS apps in Ruby is no longer actively maintained.
5. Write once run anywhere, but this time it'll really work!
I write code to build businesses, not to follow code trends. If the business needs Node.js, you betcha. If the business doesn't, why not use something that has worked for 10+ years?
http://motioneers.herokuapp.com
A lot of other info is linked from the website, plus community members have been adding examples and other content elsewhere:
I found this paragraph really hard to grep given how vague it is, but I'm assuming that he's euphemistically saying that his team/company was either not interested or not able to learn the language/framework. That would have been a more interesting article to me if he'd expanded on that.
If the team isn't interested in using some tech, then that's a sufficient reason itself to not use it. If they don't want to learn any language beyond what they're comfortable with, I'd be pretty concerned about that kind of culture, because it'll hurt them in the long-run.
If the issue is actually that they can't deliver rails projects to clients because corporate people can't write ruby, then that's more important than any other reason given in the article.
I didn't conduct a thorough analysis on the reasons why I've seen big corps rejecting Rails, so what I'm about to say is based on the the experience of being through all these projects.
But most Rails projects are connected to the innovation departments and once they passed through the PoC stage, their IT departments asked for a re-write on a tech already in their ecosystem. Supporting additional techs raises complexity and forces them to support another stack.
We were indeed able to push some Rails apps to production on enterprises, but these were usually apps that performed a specific goal for one of the departments, and once we went for the big projects within their core, tech stack was always an issue.
I could tell you why I chose to use POE access points in my house instead of plain Ethernet, it wouldn't tell you anything about when you should.
But we work on several projects by helping a lot of people at the same time. And need a solution that fits our and our client's purpose and context.
Rails did that to some extent, but I believe JavaScript will help us navigate a larger context.
I also think that the [JavaScript] community is going through a "cool" phase, similar to what happened to Rails in the early days...[A]s Rails matured, it lost it's cool factor and the community stabilised.