>I think the key difference is that frameworks usually hijack your control flow, while library are not. Which is what should be expected. The point of a frame

>I think the key difference is that frameworks usually hijack your control flow, while library are not. Which is what should be expected. The point of a framework is to not only provide higher level abstractions to rapidly put together a certain type of application but to also provide a certain approach or set of approaches (a "framework") to follow as a guide during the process. This means some generalization should exist but if a framework is too abstract its really no longer a framework... it's a library. A library is supposed to simply provide useful utilities/lego blocks to assemble however you want and not necessarily give specific guidance or patterns. Certain common patterns of usage may arrive as a sort of emergent property based on fundamental library choices/structure but it's overall pretty flexible.