3 ms·
This is actually why Rails was so successful. The world of Java was frameworks full of configuration files and Rails went with the "convention over configuratio
by brightball 5y ago
This is actually why Rails was so successful. The world of Java was frameworks full of configuration files and Rails went with the "convention over configuration" approach.
You jump from Rails project to Rails project and they all work the same way. You know where everything is immediately. It's fantastic for teams and long term maintenance between different devs because the learning curve of each project is virtually non-existent.
But Rails has gotten bigger and more complicated over the years, which makes it tougher to make the case.
- ratww 5y ago> You jump from Rails project to Rails project and they all work the same way. You know where everything is immediately. Except lots of projects today use very diverse structures and the meat of the code is often on complex libraries like ActiveInteractors, Trailblazer Operations, stuff from the Dry-RB ecosystem, etc, or sometimes (hopefully) simple Service Pattern classes, if you're lucky. Sometimes all of them at the same time. For lots of companies, Rails projects in the real world has ceased being easy to grasp for a while.
- brightball 5y agoYea, this has been my experience as well. That's what I meant by the "bigger and more complicated". Certainly set the standard for a long time though.