4 ms·
It depends what you're developing. If you develop a product (startup) that will change the world, you spend a lot of time, you put your heart into this product,
by starikovs 12y ago
It depends what you're developing. If you develop a product (startup) that will change the world, you spend a lot of time, you put your heart into this product, you should understand every line of code, so you develop a product not framework. If you create site by site every week or day for your clients, you need a framework.
- erglkjahlkh 12y agoOr, what you are building requires somewhat complex components, but you'd rather focus on something else? Many frameworks have their own component libraries. I'm not talking simple tooltips, I'm talking about real components. Sencha's tree.Panel comes first to my mind: http://docs.sencha.com/extjs/5.0/5.0.1-apidocs/#!/api/Ext.tree.Panel http://docs.sencha.com/extjs/5.0/5.0.1-apidocs/#!/api/Ext.tr... It has extremely powerful feature set (based on the other features of the framework) out of the box and you can very fast switch your focus on other things besides re-implementing the wheel. I simply haven't found some of these things as simple libraries. They nearly always come within complete frameworks, because they have had to implement a lot of stuff that really just requires other features from frameworks. And, no, I'd rather not spend a year implementing that feature set.
- ahmacleod 12y agoFrameworks are great for startups. Before market fit, they make it easy to quickly build (and tear down) functionality. Afterwards, they make it easy to integrate new members into your team. At either stage, you don't want to spend your time reinventing the wheel or teaching the intricacies of your bespoke wheel to someone else.