Nowadays most interaction is happening directly in the browser.
Rails lives of "best practices" and decisions made by experts.
But they have no common patterns for frontend logic. They stuck w/ "js.erb" for quite some time, while everyone hacked their own solution w/ backbone or ember. Now they "allow" webpack, react and co. But there is no strong integration or any benefit compared to not using rails.
Unless they introduce a radical easy way to develop frontend logic they will be reduced to "api provider" and thus soon lose their competitive advantage of being a simple/strong out-of-the-box solution.
Will they just disappear? No. PHP didn't just disappear neither. It just stopped being the thing you recommend/prefer using for new projects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nowadays most interaction is happening directly in the browser.
Rails lives of "best practices" and decisions made by experts.
But they have no common patterns for frontend logic. They stuck w/ "js.erb" for quite some time, while everyone hacked their own solution w/ backbone or ember. Now they "allow" webpack, react and co. But there is no strong integration or any benefit compared to not using rails.
Unless they introduce a radical easy way to develop frontend logic they will be reduced to "api provider" and thus soon lose their competitive advantage of being a simple/strong out-of-the-box solution.
Will they just disappear? No. PHP didn't just disappear neither. It just stopped being the thing you recommend/prefer using for new projects.