... some thoughts
Many PHP framework projects boast themselves as being "more flexible", "easy to use",
"very fast" and the like. As you may have noticed, the fastest code is the one that never runs ;-)
And how can a framework be easy to use and understand when it has thousands of uncommented lines of code and
little else? A project will be "easy to use" if it has clear and concise documentation and its source
code has extensive and meaningful comments.
This project has a lot of advantages compared with other framework projects, but we can not describe them in just a few words. They will become clear when reading the upcoming documentation and the source code if you are up to it.
Many framework projects claim that classes in a library must the independent from one another. But why? In this case, all we get is a collection of classes and not a real framework. For example the class 'email' should check the recipient's address is well-formed before sending a message. Then can it should be allowed to use the 'validate' class, which is responsible for checking the validity of email addresses among others. Or the 'form' class should have access to the 'filter' class to filter data and ensure valid html output will be produced. We think frameworks should have integrated kernels. This is what why we said this is a monolithic framework and not a collection of independent classes.
But then, you decide for yourself...
"As you may have noticed, the fastest code is the one that never runs ;-)"
Dec 31, 2013
Dec 31, 2013
Mar 29, 2013
Jan 29, 2013
Dec 1, 2012
Nov 28, 2012