3 ms·
After years of dealing with the same issue in PHP, I have come to the conclusion that frameworks should be evaluated based on two criteria: 1) How quickly can
by dools 13y ago
After years of dealing with the same issue in PHP, I have come to the conclusion that frameworks should be evaluated based on two criteria:
1) How quickly can a developer who is competent in the language (ie. a non ninja-rock-star) but has never heard of the framework understand what's going on?
2) How hard is it to take the value that I create (ie. the code I write) and move it to a different solution?
Of course the result of these is that the best framework is no framework at all... In the case of PHP, at least.... in JS it may be the case that some minimal framework is required, but as much as possible I think that libraries, more than frameworks, are the key to this issue.
- krapp 13y agoActually I think in PHP's case the best framework is at best minimal, but something more than none at all. Anything beyond Composer and a PSR autoloader to manage libraries, a router to abstract requests from the filesystem and (arguably) a templating engine is nice but not absolutely necessary. But I think PHP is a nightmare without at least that.