3 ms·
That's really too open-ended to answer. Plus the best frameworks come from solving a specific problem and generalizing, not trying to be an abstract general fra
by jerf 16y ago
That's really too open-ended to answer. Plus the best frameworks come from solving a specific problem and generalizing, not trying to be an abstract general frameworky thing from day one. Pick a project, concentrate on writing good code with DRY (Don't Repeat Yourself) and you'll naturally be writing a framework that can actually do something.
To write a framework, you need to know what problems you need to solve. You get that from trying to write websites, not from trying to write frameworks. I strongly recommend against trying to cargo-cult a framework ("well, they have ORMs and MVC and dadadada, so I'll write an ORM and do MVC and dadadada because that's how it's done"), because you may get the letter right but you'll be missing the spirit. (Not that some very successful frameworks haven't suffered from exactly that.... no, I'm not talking about any of the really big hitters, but some of the mid-tier ones have this problem.)