2 ms·
I don't know, I think you're over-characterizing this as a psychological decision. I tend to prefer libraries over frameworks for the simple reason that they're
by overgard 11y ago
I don't know, I think you're over-characterizing this as a psychological decision. I tend to prefer libraries over frameworks for the simple reason that they're usually much quicker to learn and use (because they have a single purpose), and they don't box me into patterns I don't want or need. I wouldn't categorize that as like making me a control freak or untrusting of others design decisions, its a pretty pragmatic decision.
- paulddraper 11y agoI think your reasoning falls squarely into the GP's description.
- overgard 11y agoI don't think that's really true. Not to put words in his mouth, but the GPs assertion seems to be that library vs framework tends to not matter much other than in what it says about the individual, whereas my assertion would be that choosing small focused libraries has nothing to do with ego or imposter syndrome or whatever, I just don't want to learn a massive chunk of code if I can learn a small chunk of code and get equal value.
- paulddraper 11y ago"I tend to prefer libraries over frameworks...they don't box me into patterns I don't want or need" You're confident that you're able to identify what you want and need, and how to get there. You don't need help or strong direction. In contrast, I worry about making the naive choice, and I trust that others have thought about this a lot more than me. So I tend towards things that have built-in best practices/assumptions/guidelines, i.e. "box me in".
- overgard 11y agoFair enough, I hadn't really thought of it from that angle, but I can see the value there