I suspect this one's gonna go down like a lead balloon but there y'go.
Rails, Grails, Django... I don't like using any of them. They abstract the database sure... but to what end? I find myself getting frustrated by the amount of attention I have to pay to what is happening to the backend because of my code changes.
I also hate the "and we have this template language" tendancy to reinvent stuff that should be common (I always rip that shit out and use XSLT).
I also have a strong suspicion that the simple apps that these frameworks make a lot quicker to build could be even quicker to build with a decent XForms implementation.
Discussion (5)
Are you aware of the Double Take Brothers?
Build bad apps faster.
D'A
/8->
Yeah... don't get me wrong. I use them so that I can churn out crap code in no time at all. But the optimization that has to occur later actually get's trickier sometimes because of the framework. Also feature requests are tricky... I'm really nervous about changing the data model in these things coz of the ORMs. Which is why I say XForms would be better.
nic, if you don't stop making claims I agree with I'm going to start thinking it's opposite week.
I've never used any of them, simply because reading through the instructions for not only installing, but using it gives me a headache.
My text editor works fine, and I have never seen a benchmark that showed that developer A is faster at doing X, Y, or Z, than developer B who just has random code snippets and libraries he's either picked up or created along the way, simply because he was using a framework.