Frameworks' key trait is that they impose limitations on the programmer You could say that a type system also imposes limitations on the programmer. Is a type

Frameworks' key trait is that they impose limitations on the programmer You could say that a type system also imposes limitations on the programmer. Is a type system a framework? Would you rather use a library than a type system? I think the point is rather that making a framework is much much harder than making a library. So it makes sense to first create a library to solve a problem if that is feasible. Once you are reasonably comfortable with your choices during creating your library, you might think about turning your solution into a framework. You should do that only if there is an actual benefit in doing so. I think frameworks live on a higher abstraction level than libraries. If you need that higher level, libraries are a poor fit. If you don't need it, why make your life harder in going there?