"Rails on the front-end" has been solved by Rails members (particularly Yehuda Katz) – it’s Ember.js. Same philosophy – batteries included with a focus on deve

"Rails on the front-end" has been solved by Rails members (particularly Yehuda Katz) – it’s Ember.js. Same philosophy – batteries included with a focus on developer productivity and don't reinvent the wheel. But it comes with the same catch as Rails. While Rails is not the most sexy and popular thing on the backend as Go/Node/Rust, same is Ember.js compared to React/Vue/Svelte/Next/etc. But after about 10 years of writing code, developers start to care less about sexiness and popularity and just want to provide value and build things with velocity and little friction, rather than arguing what folder structure to use or which router package to install.