> I don't think you're even being reductive; it's just irrelevant. The arguments here are: "With libraries you call the code; with frameworks they call your c

> I don't think you're even being reductive; it's just irrelevant. The arguments here are: "With libraries you call the code; with frameworks they call your code" "This isn't a good distinction because there are lots of things we wouldn't consider frameworks that call your code" That seems relevant to me. > I'll spend a lot more time and money on making my application than I will thinking about how the Linux kernel works. That means the kernel is doing its job, and if you swap out "Linux kernel" with "Django", that would also mean Django is doing its job. Without the kernel, you'd have to do a lot more work talking to hardware and scheduling other processes to run. Without Django, you'd have to do a lot more work wrangling HTTP and SQL. It feels like peoples' issue with frameworks are that they force a way of thinking on you. But everything in software does that, the semantics of processes, pages, threads and so on are entirely made up, just like model view controller is.