2 ms·
That's the difference between using a simple, straightforward framework and "magic" framework. A well designed framework should expect that its users are going
by jmtulloss 17y ago
That's the difference between using a simple, straightforward framework and "magic" framework. A well designed framework should expect that its users are going to need to dig through the internals and should design accordingly. It also should not force you to use any particular abstraction if you don't want to. Don't need an ORM? Don't use it.
- fauigerzigerk 17y agoSorry, but you are just repeating framework marketing fluff. Have you read what I said about generalisation at all? Frameworks _must_ generalise further than I do in any particular project because they cover a much wider range of cases. It's not just "magic" frameworks or badly designed frameworks, it's simply the logic of what frameworks are. Therefore this claim you make is just not true: "but if you didn't have the framework, you'd have to learn all that just to get your app off the ground"