4 ms·
I think it is more accurate to say he wrote his own library. These terms are not well defined (AFAIK) but often a framework implies that you have something “al
by sorbits 16y ago
I think it is more accurate to say he wrote his own library.
These terms are not well defined (AFAIK) but often a framework implies that you have something “already running” which you customize by providing callbacks, delegates, and similar.
With a library you have a set of reusable functions and data types (classes).
I think an Apple engineer referred to frameworks as “the hollywood model: don’t call us, we call you”.
For PHP programmers that dislike the framework model, have a look at http://flourishlib.com/ http://flourishlib.com/ — been mentioned on HN before but I hadn’t seen it before this week. In philosophy this is exactly how I prefer a good library of re-usable code: lots of self-contained functions and data structures which each solve a problem, and you decide when to use what.
- wanderr 16y agoYes, I think a huge part of the problem wih frameworks for a lot of programmers, myself included, is a lack of control. The framework takes control and you have a certain set of ways to modify its behavior. If what you need to do isn't something the framework designers had in mind, you may have to hack the framework. Even if it is something they had in mind, it can be much slower to hunt around and find the 'right' way to tell the framework to stop doing this automatic thing and do this other thing instead. It is often much faster for an experienced and skilled developer to write something that just does what they need to begin with. Libraries, OTOH, don't presume anything about taking control. You're still the driver, they just have a lot of things that can make your life easier if you choose to use them.