Hello! I teach quite a few people Rails through my class, Epicodus. One thing I've noticed is that the sheer number of files and folders `rails new` generates is pretty intimidating for newcomers to Rails. I'd like to make a few suggestions to how to reduce that intimidation.
1. Don't create the `tmp` and `log` folders. These are automatically created when `rails server` runs for the first time, so there's no reason `rails new` needs to generate them. 2. Combine `boot.rb` and `environment.rb`. I'll be the first to admit I don't understand the Rails boot process as well as I wish, and there may be implications to this I don't understand. But in my informal testing, moving the contents of one file to another works just fine, and I personally having trouble seeing the distinction between the two. 3. Remove internationalization by default. I could be totally off-base, but this feels like a feature that probably isn't used by a majority of apps, and could easily be added by more experienced developers who need it (and a Rails generator could be built to easily re-install it). 4. Move binstubs logic into the Rails gem executables. I haven't played around with this yet and could be wrong, but I don't see why these files need to be added to every app, when their logic could simply be included in the rails/rake/bundle/spring gem executables. The result would be a much simpler file/folder structure for a new Rails app: -app -config -db -lib -public -vendor Gemfile Gemfile.lock README.rdoc Rakefile config.ru and a simpler `config` folder as well: - environments - initializers application.rb boot.rb database.yml routes.rb secrets.yml which, in my experience/opinion, would make it much easier for devs to get going with Rails. I'd love to get other folks' thoughts on these suggestions, and if anybody is interested, work together on implementing those that others agree make sense. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
