Developer opinions
David Hainemeyer Hansson says in an article called Can software have opinions?:
…
Because when I adopt software, I’m not just looking for features, I’m looking for approaches too.
…
The closer your opinions on web-application development are to mine (and that of the growing community), the more Rails will feel like the perfect fit.
It is interesting, since I was talking about Rails today with a colleague and I was trying to convince him why it is really a far better aproach than others I have tries (Delphi’s Websnap or asp.net). I tried to show him the beauty of the routing stuff or how easy is to cache actions or partials because of the controller action/view separation etc.
Perhaps I was wrong, perhaps he couldn’t see it because of his opinions on (web) development. Perhaps I am just more ready or “cooked” or experienced or only just more close to the opinions expressed by the Rails people (through their work).
Having said that, and in the spirit of the Agile manifesto, I think that a framework should accept and follow some slightly different opinions of the developer on some issues. It’s like the ActiveRecord Rails implementation. It has some conventions (as the names of the classes/tables) but if they don’t fit your design (read opinion) you can override them.
