4 ms·
Framework is a thing that should emerge as a result of your own project long after its launch (after major evolutionary changes/rewrites based on actual usage f
by schiptsov 15y ago
Framework is a thing that should emerge as a result of your own project long after its launch (after major evolutionary changes/rewrites based on actual usage feedback). It is your team's encoded skills and experience.
People who are trying to choice a framework by browsing trough feature lists (not even the code) before they have a working prototype (which means understanding of actual algorithms and data structures) are doomed. ^_^
People who're trying to sell you a piles of code "you really-really need" such as J2EE are just cheaters.
btw, no one prevents you from copying the code from any codebase you like, but only if you can read and understand it. My favorite example is libnginx.so - just better APR. ^_^
- praptak 15y ago"Framework is a thing that should emerge as a result of your own project long after its launch (after major evolutionary changes/rewrites based on actual usage feedback). It is your team's encoded skills and experience." This, expressed by Martin Fowler: http://martinfowler.com/bliki/FoundationFramework.html http://martinfowler.com/bliki/FoundationFramework.html and http://martinfowler.com/bliki/HarvestedFramework.html http://martinfowler.com/bliki/HarvestedFramework.html