[evolve2k]

Coming from Rails, which I’m sure informes part of the philosophy I really like this.

One design value of Rails is “Convention over configuration”, or what I sometimes explain as smart defaults over having to decide everything.

I see this is an area this project can help with; thought through folder and naming conventions; wrestling with issues at the seem between common tools. Making doing things the right way way (like database migrations) becomes the easiest way to do it; most of the time.

A bundle of smart conventions and ways of working that cuts down yak shaving and sometimes solves arguments as the project can be; well we thought on this a lot more than most of you and we’ve gone with this approach to stick these together and if you only half care now you can get this done for free for your apps.

[elliotec]

This is like, the opposite of Rails and the "convention over configuration" style. It's making no decisions for you except to "use primate in the middle of whatever else you decide to configure!" Seems like it's actively encouraging making a mess of your stack. I don't understand it at all.

[evolve2k]

I don’t read it that way. I think they are just cutting the edges of what are “the core tools” of the stack in different places.

This projects ability to introduce conventions cause there is a framework underlines its potential value.

If folks that are experimenting across any of these tools start to choose to begin from this framework first; then there’s really opportunities for this to grow. Either way I’d suggest that’s a good focus for them to measure success.