[ryanbrunner]

This to me is what I really miss about Ruby on Rails being a more popular platform, way more than any of the metaprogramming magic or super-readable syntax. It made a ton of choices for you, which helped with productivity on teams more than anything else.

If you had a new developer coming onto a Rails project, there's no need to ask how logging is done, where models and controllers were stored, what the naming convention of database tables were, how assets are compiled, where to find tests or how to run them, how to start your application, or probably a hundred other little tiny decisions.

Sure, you have less control over things, but 90% of the time, that control doesn't matter, and you're making life more difficult for every other person who will ever read your code in the pursuit of what's often purely aesthetic.

[samwillis]

It’s the same reason I love Django (no tooling decisions to make) and hate “modern” JavaScript development (far to many options for small tools to construct a framework).

What is the opinionated framework of choice for front end work now? (Something that is all in like Django or Rails)

[arendtio]

Maybe Ember.js - https://emberjs.com

Yehuda Katz is Core Team Member of Ruby on Rails and Co-Creator of Ember.js https://yehudakatz.com/projects/

[thedanbob]

My org still uses RoR for nearly all our sites. I used to add a fair amount of custom config and gems, but more and more I find myself gravitating to the default stack. It’s just simpler, and easier on the next guy if I ever pass on a project.

[3pt14159]

And the real magic is that if you really wanted that control back you can have it! Nothing stopping you from opening up a class and redefining a method for what you need.