Thanks for the feedback. Reading the post again, I realize that what I wrote didn't actually match up with what I meant. I meant more that the reason frameworks

Thanks for the feedback. Reading the post again, I realize that what I wrote didn't actually match up with what I meant. I meant more that the reason frameworks are often bad is because "Frameworks are more likely to not handle all use cases" AND "The effort required to patch a framework to accommodate the functionality you want is often higher than the effort to put all the libraries together yourself" (because of complecting). Or worded another way, "Frameworks are more likely to not handle all use cases [that are within their scope]." Certainly a single library is not going to handle all the needs of your app, but it will hopefully handle the things it's intended to handle without too much need for modifying its behavior. e.g. if I need to use websockets, I can just use Sente without bending over backwards to make Sente work for my particular use case. That's not very clear from what I've written though, so I'll update the article.