>>Every week the developers want to switch out some module for another module within Rails because it was the hot new thing. You misunderstood DHH's point. He'

>>Every week the developers want to switch out some module for another module within Rails because it was the hot new thing. You misunderstood DHH's point. He's talking about well-integrated defaults. He isn't talking about preventing people from using other modules if they choose to do so. I mean, if your developers want to try the hot new thing every week, Rails isn't the problem. That much should be obvious.