[LRUG] Does Rails have an image problem?
ed.lepedus at googlemail.com
Mon Aug 17 08:29:15 PDT 2020
Once again I’ve recommended Rails for a project, and once again, I’ve found it a really hard sell, and I suspect the decision will be to use NodeJS instead. It seems that outside of the Rails community, most devs have a pretty poor opinion or just lack of visibility into the awesomeness of Rails. I’ve been asked questions like “Isn’t Rails abandonware now?”, been pointed to StackOverflow’s developer survey (https://insights.stackoverflow.com/survey/2020#technology-most-loved-dreaded-and-wanted-other-frameworks-libraries-and-tools-loved3 <https://insights.stackoverflow.com/survey/2020#technology-most-loved-dreaded-and-wanted-other-frameworks-libraries-and-tools-loved3>) as ‘evidence’ for NodeJS’s superiority and been told that “the majority of Rails consultants make their money on migrating people to other platforms”. This is not a new thing. I’ve been recommending Rails for web projects for nearly 7 years, both as an employee and as a consultant, with zero success. And before you think it’s just my credibility, I’ve not had any issues when recommending, WordPress, NextJS, Kubernetes, Ansible etc. It’s just Rails.
My current team would benefit hugely from Rails. It would do wonders for everything from code quality and productivity to documentation and our ability to hire and onboard new developers, but I fear that we will once again default to NodeJS and miss out on most of those benefits.
The weird thing is that we use and love systems written in Rails, such as GitLab, and have enthusiastically committed to migrating our forums to Discourse, but the halo effect from those projects doesn’t seem to be affecting perceptions of Rails itself.
How do you sell Rails in a compelling way?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Chat