[frje1400]

Perhaps "frameworks don't compose" and "frameworks shape how you code" are actually good features, not a problem. Where are frameworks the most popular? Probably for web services (e.g. Spring Boot for Java). You don't need them to compose because you will only have one.

That you are forced (or at least strongly nudged) to code in a certain way is good because that means that all your web services are at least superificially familiar to all developers at the organization. That special service composed from many libraries? Impossible to work on without significant time investment.

I suppose though that if you are in a domain where you actually would want a library, but all that's on offer are frameworks, and you actually need to compose them, then yes, that seems problematic.

[gblargg]

Expanding, a framework allows components to work together, the OS being the most common example. Most languages also define a framework for the program to fit into. Startup initialization, main routine, shutdown, memory allocation. Without this it would be hard to use libraries.

[cjblomqvist]

A solution is to develop frameworks as a set of libraries + some (best case very little/no) glue code. Eg. ASP.NET vs EF Core.