Hacker News new | past | comments | ask | show | jobs | submit login

Sure, maybe if you've never done it before because it's a learning experience, but it's a patently horrible idea otherwise.



It isn't a horrible idea. Using a ready made framework all the time without regard if it's right for the job is a horrible idea.

For some apps which have a certain level of complexity and require some extra flexibility, you end up wasting more time fighting the framework than getting the job done.

It helps if you have a well defined standard in place, for python, that means WSGI. Coupled with good libraries, it's hard to beat.


Right, but that's not "writing a framework", it's "using existing libraries in conjunction with one another". There's no real "magic", directory layout rules, etc.

Maybe you end up writing a couple scripts to tie them together or something, but it's hardly a framework. And in many cases, yes, it is a better choice than a framework. And still a better choice than writing your own framework.


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 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.


Right, your new rule is, write you own framework/library if necessary, otherwise use what's there. That's much better than your original rule which ruled out any use of frameworks as no frameworks could ever have been created.

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.




Consider applying for YC's first-ever Fall batch! Applications are open till Aug 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: