I don't even think this is like a thing to debate about. They're not the same thing. I've been a developer for near 10 years. In that time I've worked on a h

I don't even think this is like a thing to debate about. They're not the same thing. I've been a developer for near 10 years. In that time I've worked on a heck of a lot of different applications. The funny thing, is in that time I've written the same code time and time again. A bit different each time, but none the less similar function. That code though, it's not something that can be replaced by a library. That's because it IS the code calling the library. If a library is a water heater, the framework is the duct work. So frameworks to me give me a way to write a lot less of that code, and to write a lot more of the code that makes my application useful. I've been brewing my own framework, for doing a very particular type of application that I tend to somehow write quite often. I wouldn't tell people to use it for everything. But for the things I use it for, it is perfect. The speed that I can iterate at has given me a name at my various employers.