When you have a good hammer everything looks like a nail. And arguably, that's the main problem with the positioning of Rails - it's often seen as a solution to everything, which is of course not true. But this is easier said than done, just a little while ago I found myself doing a dinner napkin sketch of a blog controller with trackback, ping, and comment modules. And you know what, it looked good on paper! However, I wasn't building the 'typo/wordpress/typepad' killer, the blog controller was an add-on for a Rails project, and that's when it hit me: why Rails?

My project wasn't about building a better blogging tool, hence my time would be better spent on features that really matter to my users. Furthermore, I couldn't possibly cover the same feature set as Wordpress or Typepad in the little time that I had. Hence, a new napkin appeared on the table, this time with a single word: wordpress, which also happens to be my favorite publishing platform.