It doesn't suck
This "framework" was written for the same reason every PHP framework
(even PHP itself) was written: Hubris. We're annoyed by what's out
there and know that we can do better.
Thus, the framework was written with the following things in mind:
PHP does a *lot*. This framework tries to do very little. You won't
find reimplementations of common tasks like fetching request
parameters (just use $_GET, $_POST, $_PUT, etc).
Putting things into the core of the framework means that they should
be important. Just as much care was spent in
thinking about what didn't (and doesn't) go into the framework as
what did (and does).
Simplicity is key. There are no vast class hierarchies designed to
meet every conceivable need for any type of functionality.
Observability is key. It is extremely valuable to be able to see all
the resources a page uses without having to trace code through four
components in ten files.
Flexibility means not forcing you to do things one way. Other than
some basic conveniences, you shouldn't be locked into a particular
style of coding.
The exception to the rule: Convention is key. Tasks should be done
in a similar fashion throughout a project as much as possible.
Documenting how to develop for an application is just as important
as what the application actually does. If new people don't know how
to work on the project, it's doomed to waste time being rewritten.
Read the documentation »
Dive into the code »