4 ms·

This is such a clean mental model that I was skeptical. I started scrutinizing it and found myself thinking about how it omits some deployment choices. I realiz

This is such a clean mental model that I was skeptical. I started scrutinizing it and found myself thinking about how it omits some deployment choices. I realized that this is a good thing, because the development and deployment choices have one big difference: development choices require rewriting when you change them. http://benatkin.com/2013/01/14/steve-klabnik-on-rails-stacks/ http://benatkin.com/2013/01/14/steve-klabnik-on-rails-stacks... Thanks for this article, Steve.

steveklabnik 14y ago
> This is such a clean mental model that I was skeptical. This is a great compliment, thank you. I mostly left deployment out because that's not part of Rails' domain: Rack lets us not care about that when building things.
- benatkin 14y ago
  I think it was a good choice to include PostgreSQL even though you can make an app DB-agnostic with rails. It's one of the defining differences between the stacks. I would really like to switch to PostgreSQL on a project I'm working on for future development even though MySQL is working fine now, and this makes me feel more confident about bringing it up to my team.