I think your post explains (perhaps unintentionally) why I've never really come to like working with Ruby on Rails as much as I liked working with Django. Or at least continue to feel less productive with it (despite liking Ruby).
Somehow the right amount of configuration seems to save a lot of work as compared to conventions that fall just short of actual need.
I think there's a trap, though, that leads to the 'convention over configuration' one-size-fits-all road, and it's things that require loads of annoying, hard to manage, poorly structured configuration. (Things, like, for example, Apache, IMO.)
Though perhaps I'm just not good at determining when to write my own generators and when not to, I've also had Rails applications where I wrote a generic controller that covered a dozen-plus models and wondered why there couldn't have just been a generic controller built in to begin with (it's not like it'd preclude bumping things out of generic into their own controller if necessary).
I kind of wonder, too, if the evolution towards things like Docker/CoreOS with stuff like etcd from more traditional Linux distros and virtualization might also be viewable as a trend from convention towards a 'right amount' of configuration.
Comments
I think your post explains (perhaps unintentionally) why I've never really come to like working with Ruby on Rails as much as I liked working with Django. Or at least continue to feel less productive with it (despite liking Ruby).
Somehow the right amount of configuration seems to save a lot of work as compared to conventions that fall just short of actual need.
I think there's a trap, though, that leads to the 'convention over configuration' one-size-fits-all road, and it's things that require loads of annoying, hard to manage, poorly structured configuration. (Things, like, for example, Apache, IMO.)
Though perhaps I'm just not good at determining when to write my own generators and when not to, I've also had Rails applications where I wrote a generic controller that covered a dozen-plus models and wondered why there couldn't have just been a generic controller built in to begin with (it's not like it'd preclude bumping things out of generic into their own controller if necessary).
I kind of wonder, too, if the evolution towards things like Docker/CoreOS with stuff like etcd from more traditional Linux distros and virtualization might also be viewable as a trend from convention towards a 'right amount' of configuration.
Just some off the cuff thoughts.