Rails comes with a default structure that serves well a ton of apps, but
does not mandate that you use that structure as is, which is a common
misconception/starting point in talks, posts, etc.

Those are the defaults, but of course projects can add their service
objects, form objects, decorators, and whatever they want. Tailor-made for
their needs or their personal preferences, which are legit.

What it is not going to happen in any foreseeable future is that the
default structure changes. The only change in that direction has been to
add a convention for code organization via modules (concerns).

I'd like to add I've personally done dozens of (gasp) well-written apps
using the default layers in the last decade, do not believe every
generalization or theoretical argumentation you read out there. Think with
your editor.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Reply via email to