Rails, shall I compare thee to a summer's day... 0
Let me get this right out front– I love Rails
My days were mired in a endless succession of javac compile cycles, huge bloated IDEs, xml config file madness, build hell, etc. Then I found Rails, and I’ve never looked back.
I love everything about Rails- the overriding philosophy of convention over configuration, the extraordinary thought and care that has gone into the API, and the seemingly endless joy of discovering new aspects of the API or even the Ruby language itself. Beyond all the technical arguments that might make Ruby and Rails the right choice for a given web application, the most important point of all is that Rails makes happy programmers. DHH has said it elloquently in his presentations, and in the Optimize for Happiness section of Getting Real-
A happy programmer is a productive programmer
This is absolutely, 100% true. Programmers are, by nature, self-motivated and driven by what inspires them. If you put them on a new framework with as much ellegance and depth as Rails, their productivity will go through the roof.
I have yet to meet anyone who tried Rails and didn’t get the bug almost immediately. On the contrary- most of the sad stories you hear about Rails involve technologists who find Rails and fall in love with it, but then can’t convince management to take a risk on it. Well, I’ve got the perfect solution for that- become management.
So there you have it- I’m a complete Rails nut. So don’t expect any blog entries about the latest C++ or Java developments- I’m sticking to what I love.
