Content originally published here : https://bootrails.com/blog/why-is-rails-not-more-popular/
Intro
I once had a conversation with an A...
For further actions, you may consider blocking this person and/or reporting abuse
I appreciate your mention of "UI-driven development". Sometimes, React apps could be equally well-made with Rails and StimulusJS. However, splitting front-end (developed as an SPA with a front-end framework) and back-end proves more beneficial in some cases. This is mainly because managing numerous Stimulus controllers and ERB partials can clutter the codebase. Based on experience, front-end work often takes three to four times longer than back-end, especially with complex UI tasks like editable tables or planning tools. Even in full-stack Rails projects, front-end time can exceed back-end work. The split approach's key advantage is better decoupling of front and back ends, enhancing UI component reuse, teamwork, tool and dependency management, and streamlining the development and maintenance process.
I worked with Ruby on Rails from around 2015 to 2018. After that, I transitioned to being a front-end React developer. Now, in 2024, I am feeling bored and tired of the JavaScript ecosystem. I miss Ruby and Rails immensely. I've been trying to persuade people, especially junior developers, to use Ruby, but as you mentioned earlier, they don't see the need to switch languages. Now, I am going back to re-skill in Ruby and Rails. This is the technology stack that I love.