3 ms·
Sure, libraries don't need to worry about hooks, but they do need to worry about providing sufficiently flexible APIs for use in different contexts instead. Soo
by Silhouette 18y ago
Sure, libraries don't need to worry about hooks, but they do need to worry about providing sufficiently flexible APIs for use in different contexts instead. Sooner or later, you've got to connect up your custom logic to the library/framework's general logic.
I guess the distinction just seems rather artificial to me. It may theoretically be riskier to use a framework, in the sense that working around its limitations may be harder to do in the worst case. However, if you're working with bad interfaces and reluctant support, and the library is of any significant size and complexity such that you couldn't just reimplement it yourself in a worst case scenario, then you're basically screwed either way. Being only 75% screwed instead of 85% still doesn't ship your product. :-)