5 ms·
I went through this exercise recently, looking for a stack for a greenfield project which I had full control over. Tl;dr: I chose Rails, albeit with ViewCompone
by ksajadi 4y ago
I went through this exercise recently, looking for a stack for a greenfield project which I had full control over. Tl;dr: I chose Rails, albeit with ViewComponents.
When I compared the existing frontend backend stacks like Svelt, Next, or a Go, Rust, whatever backend + React frontend, the amount that’s in Rails out of the box is just not even close to the rest. From ActiveRecord to secret management, a dynamic ecosystem of gems for almost anything and much more, choosing another stack just didn’t make sense.
Believe me when I say I really wanted to choose React for frontend because of its community and ecosystem but for an app with a backend that there is so much Rail does for you that you’d be spending weeks rebuilding with anything else.
A caveat is that this is Rails + Hotwire and Turbo + ViewComponents that makes it a no brainier. The old school Rails MVC would have been a harder sell