3 ms·
I don't agree with this simplistic distinction between framework and library. There are plenty of libraries that call back into user code. A better definition m
by flohofwoe 4y ago
I don't agree with this simplistic distinction between framework and library. There are plenty of libraries that call back into user code. A better definition might be that a framework imposes an entire 'application model' on you, and trying to step outside that predefined model is at your own risk, while a library is a much smaller and flexible building block (also a building block for frameworks).
But there's a large gray zone between these two, and eventually the distinction is also often quite pointless in the real world.
- valenterry 4y agoI think the last sentence is really true. And yes, there are libraries that call back into user code, which makes them framework-like in this regards. > A better definition might be that a framework imposes an entire 'application model' on you, and trying to step outside that predefined model is at your own risk This is the kind of definition were 50% will call something a framework and the other half will call it a library then. Not sure if that is really helpful.
- 8note 4y agoThis kinda suggests that most node modules are in fact frameworks, in that they accept callbacks. Callback hell however, is not something I'd associate with a framwork
- valenterry 4y agoYeah, if this is not just an once-off async callback (where you could just use a promise) but somthing more complicated, then this is indeed more framework-like and for me would be a reason to try to avoid it.
- Someone 4y agoAnother, a bit less gray zone, distinction is that you can have only one framework in your program, but can use multiple libraries.
- mobiuscog 4y agoIn the Java world, at least, you can absolutely have multiple frameworks in your program.
- schwartzworld 4y agoYou can have multiple programming languages in a program, so of course you can have multiple frameworks.