・your code call libraries ,frameoworks call your code
・framework==>Don't call us, we'll call you
framework
===>
Frameworks are not the cure for all programming
problems. Putting aside today's awesome state of
development, you should always remember how
frameworks were created a few years ago. Most of them
were more or less unoptimized junk created by one guy to
help him speed up his development process, without much
care for documentation, elegance, ease of use, or even
readability of his code. Then another group of guys took
this code and bloated it with a patchwork of extra
functionalities barely consistent with the original code.
Then it became apparent that this whole lot needs a solid
cleanup in order to be usable, but this would mean either
rewriting it from scratch or packaging code in additional
wrapper classes, further increasing its unnecessary
complexity.
Of course, today the disorganized origin of frameworks is
not as evident as before because the quality of code has
risen considerably. But still, that's why most beefed-up
frameworks have performance issues. That's why they are
39
www.it-ebooks.info
not always easy to learn. And that's why new ones emerge
to cover up weaknesses of older ones. And finally that's
why major frameworks provide completely rewritten 2.0
versions, which address all previously mentioned
problems.