The way we built DEV with Ruby on Rails and vanilla at first on the frontend while gradually figuring out identity and path for frontend code is still a pretty great idea for similar use cases.
There are no shortage of Rails-driven sites thriving these days, meaning the technology is getting a lot of resources thrown its way. This has been the case for years, but I feel like the very successful launch of hey.com from the core Rails team of Basecamp is a real boon to the whole ecosystem.
I like Rails the technology, the API, the choices made, but I love the health of the ecosystem these days.
The way we built DEV with Ruby on Rails and vanilla at first on the frontend while gradually figuring out identity and path for frontend code is still a pretty great idea for similar use cases.
There are no shortage of Rails-driven sites thriving these days, meaning the technology is getting a lot of resources thrown its way. This has been the case for years, but I feel like the very successful launch of hey.com from the core Rails team of Basecamp is a real boon to the whole ecosystem.
I like Rails the technology, the API, the choices made, but I love the health of the ecosystem these days.
Come one ! I completely agree, Rails is most robust and mature framework I ever used. Battle-tested by Dev.to, Basecamp team (also Hey), Github...
It's worth it !
Shopify, probably the biggest Rails user/driver from my perspective, is now a 100 billion dollar company and counting.