4 ms·
You're too kind. Frameworks are the reason I can go and build a top class product in 6 months all on my own. If we didn't have them, each new product would req
by nikster 13y ago
You're too kind.
Frameworks are the reason I can go and build a top class product in 6 months all on my own. If we didn't have them, each new product would require an army of programmers re-inventing wheels, and only big corporations with lots of money could afford to even attempt it.
Frameworks rock. Abstraction also rocks. Whenever I need something more than once, I make it abstract. I automate it, abstract it, make it re-usable. And 99% of the time - I am not kidding, it's really that high - I will re-use that piece of software, re-run that script, etc.
A senseless article, all in all.
- fauigerzigerk 13y agoFrameworks have a lot of issues. First of all, they tend to exclude each other, hence preventing you from reusing code that might be a better fit for a particular problem. Second, they provide a perverse incentive to force every new application feature into the structure of the framework you decided to use at the beginning of the project. Frameworks are like debt. They give us a head start at the cost of paying more down the road. Sometimes that head start is worth the higher overall cost and sometimes it's not. I think libraries are a lot less problematic and still provide most of the benefits of frameworks.