* What was your decision-making process when evaluating frameworks? very clean internally framework code. not necessarily large user base. something where th

* What was your decision-making process when evaluating frameworks? very clean internally framework code. not necessarily large user base. something where the original devs may likely still be using their creation within the next two years. lightweight. no magic!!! * Was your ultimate choice made simply because the framework was the defacto in your language of choice? In other words, did you choose Rails for Ruby, Django for Python, Cake for PHP, just because the language itself was what you knew? Two years ago, I wanted ruby, but not rails. I settled with rails and moved on to merb once that was available. * Assuming you're sufficiently experienced in framework X now, what are your regrets? What makes the other frameworks look like greener grass? I have a background in writing and choosing frameworks. So I knew rails was not a fit before I used it but it was all there was if I wanted to go with ruby. Merb still is a fit despite its relative neglect this year. I have few regrets continuing its use. * If you could start your project over again, would you chose the framework again? I am doing a new project now, I'm using merb again because I have invested in it and it works well. If I were to move on, it would be for a javascript framework as I should benefit from javascript client and server. Such js frameworks are not mature enough for my needs. * Did you choose framework X secretly because you just wanted to learn it? In other words, was it attractive to you just because all the cool kids were doing it and you wanted to add it to your toolbox? Be honest. no. I'm cool enough as it is ;).