4 ms·
The difference is that the framework is built to be an open source framework - it has general abstractions. Your own patterns and practices are developed to ap
by pags 12y ago
The difference is that the framework is built to be an open source framework - it has general abstractions.
Your own patterns and practices are developed to apply directly to what you're building.
- acjohnson55 12y agoBut a good framework has well chosen abstractions that took many person-hours to settle upon, a community of engineers working to perfect it, and probably uncountable hours of production battle-testedness.
- pags 12y agoI'm not sure that time and bodies necessarily produce good abstractions.
- jdlshore 12y ago> has well chosen abstractions That's a rather large leap of faith. It's more likely that it has a bunch of abstractions that were chosen early in the project when the maintainers were young, dumb, and eager; that have since shown their age and have been worked around repeatedly; but can't be removed due to being core to the framework and having a large body of applications depending on them.
- acjohnson55 12y agoNot all frameworks. Good frameworks. The best incorporate the lessons learned from working with previous frameworks.