DADanielKehoe·Feb 9, 2013
It is interesting to see this approach.
Seems a lot of interest this week in exploring approaches to Rails starter apps: Cristiano Betta's Primo [1], Carbon Five's Raygun [2], this script from TaskRabbit. So I updated two lists I maintain:
A list of starter apps:
http://railsapps.github.com/rails-examples-tutorials.html
A list of various template-generating gems and application templates:
http://railsapps.github.com/rails-application-templates.html
Two observations, if I may. First, it's very interesting to compare the commonalities and differences among the various starter apps, in light of discussion of "Rails is omakase" (@dhh) and "Rails has Two Default Stacks" (@steveklabnik).
Second, most starter apps end up mired in the tar pits of neglect, abandoned in the constant change of Rails and its gem ecosystem. Building a starter app, an
Read the rest
application-generating gem, or an application template is the smaller challenge; maintaining it is the bigger challenge. To that end, a starter app needs a large communal open source effort to stay fresh and up-to-date. Most projects have failed on this count.
[1] https://github.com/cbetta/primo
[2] https://github.com/carbonfive/raygun