111–120 of 142 posts
Java, so I prefer Wicket and like Stripes.
Used wicket for a while on xp-dev.com, but moved to a home grown one as wicket was a tad bit too bloated.
But I really like how wicket is component based, and have used it successfully for other project (all intranet based ones though - so don't really have many publicly accessible examples)
Pylons. http://pylonshq.com/
Never used a framework and never will. I know how to code. I do my own sites and don't use others or have others do my work for me.
i dunno why u got downvoted for just being different shrug
The main reason people use frameworks, is not because they're lazy or bad, it's because it lets them get more done, faster, and with less tedium.
CakePHP for PHP. Definitely the best PHP framework out there, in my opinion; fast, good installed base made out of all-star clients (Mozilla, Yale, others), not restrictive or cumbersome. Honestly, though, I try not to use PHP.
Earlier quoted context omitted.
Haha...I assume you're kidding, right? Are you coding in binary? Because if not, someone else has "done your work for you" :)
Coding in binary on what? Unless you mined your own raw materials to build your machine, someone else has "done your work" for you. Not to mention where you'd get electricity...
To do your own work, use your fingers.
Earlier quoted context omitted.
Sure, maybe if you've never done it before because it's a learning experience, but it's a patently horrible idea otherwise.
So that means frameworks shouldn't exist at all in your opinion?
Basically, I'm saying if you're using a language which has mature frameworks and/or mature libraries which could be forged into an ad-hoc framework (templating, serving, ORM, etc.) it is terrible advise to tell people "just write your own".
Only in the case that you've considered all existing (relevant) options and determined none of them meet your use case (and none can be minimally altered to do so) should you consider writing your own. Anything else is a waste of time and effort.
Earlier quoted context omitted.
So that means frameworks shouldn't exist at all in your opinion?
Erm, that's my opposite opinion, I guess. My (attempted) argument is that one should not write their own framework unless doing so as an exercise in learning. In any other case, using existing frameworks or using the "roll your own library mix tape" strategy is far more efficient. Basically, I'm saying if you're using a language which has mature frameworks and/or mature libraries which could be forged into an ad-hoc…
But Im' still not happy :) I'm sure a lot of popular frameworks were created without any necessity, simply because they were fun to make. Some turned out to have qualities that nobody (including its creator) would have been able to spell out beforehand.