Great post! I agree with your argument regarding libraries over frameworks, but I think the real problem is how we couple our software to third-party libraries. Frameworks tie you down more than a library, like you said. But if you're not careful a library can do just the same. Which is why I believe developers have to be more clever when architecting software.
Reading your post reminded me of Robert C. Martin (Uncle Bob) opinions on how coupling your code with anything that can screw you over obviously is a bad idea.
"Apparently the notion that it’s a good idea to hide the framework, UI, or database from the application code is not universally accepted."
"What happened to us? How did we forget these rules? When did the old rules of coupling and cohesion evaporate from our awareness? Are we really so naive as to think that the best way to write a complex system is to throw a bunch of components into a bag and shake it until it works?"
Reading your post reminded me of Robert C. Martin (Uncle Bob) opinions on how coupling your code with anything that can screw you over obviously is a bad idea.
"Apparently the notion that it’s a good idea to hide the framework, UI, or database from the application code is not universally accepted."
"What happened to us? How did we forget these rules? When did the old rules of coupling and cohesion evaporate from our awareness? Are we really so naive as to think that the best way to write a complex system is to throw a bunch of components into a bag and shake it until it works?"
http://blog.8thlight.com/uncle-bob/2011/11/22/Clean-Architec...