I've been a Drupal developer for a while now. I've been recently playing with Rails because that's what I wanted to be doing in the first place, but just didn'

I've been a Drupal developer for a while now. I've been recently playing with Rails because that's what I wanted to be doing in the first place, but just didn't know enough about enough to be able to really get it. Thanks in no small part to working with Drupal I now know enough about enough to be able to get some stuff done in Rails. And the more I work with Rails, the less I'm interested in working with Drupal in the long-term. So much of working with Drupal is just overriding what Drupal wants to spit out instead - here's this Views markup, or this user registration process, or this database schema, now customize it to your liking. Rails takes the exact opposite approach - here's nothing, now make what you want. As my abilities grow, I'm coming to greatly appreciate the second approach. Perhaps it's the author's experience with other modern development tools rather than a misunderstanding of Drupal that's informing his bias.