php - Arguments for not using a framework -

php - Arguments for not using a framework -

a little while ago read great article described number of reasons against using of rad frameworks available php. basically, argued framework should off ground quickly, , should out of way. none of php frameworks did that. pointed out django @ doing (but that's not php framework).

for life of me, can't find article now.

so i'm curious. have solid arguments why applications should not built on top of rad framework? , i'm not talking generic applications (frameworks definition seek solve generic problem. quesiton translate specific problems).

and when built on top of, mean ground based on framework. don't mean referencing framework series of libraries. mean basing entire architecture of application off of framework (which ties framework).

i'm not talking rapid prototyping code re-written anyway. i'm more looking @ long-term applications have specific business requirement meet, , must supported , maintained (and modified) relatively long period of time.

we hear why should using framework. there reasons galore:

not reinventing wheel (although hate reason) faster development time (since architecture skipped) easier bring new developers in common problems solved etc...

but i'm looking antithesis...

any thoughts?

it implied frameworks beingness written unknown heroes smarter default. matter if fact it's not true. has bugs, can messy , unnecessary overcomplicated. thus, having own helper library more handy using such monster, knowing 10% of it's features.

php architecture frameworks