So? My ORM can easily be improved. I'd like to see you code a whole framework from scratch. Only half the router and the template engine is not by me. Even though the ORM includes unnecessary coding, it's still faster than PropelORM for simple purposes as inserting, updating, fetching and so...
Nothing hehe, I just liked the http://redbeanphp.com usage more, and wanted to code one alike but with some twists and less coding.
#UPDATES
I've managed to find an easy way to receive columns/rows/values from a table based off the same structure as the insert method above.
$user =...
Argh mate, already at first it's slower.
You're initializing your classes before they're even used. Aswell as an IoC and PropelORM is slow, it's not even going to be close. You can't optimize libraries you haven't coded to perform better, unless there's configuration to do so, which I highly...
#UPDATES
Couldn't really find an appropriate ORM that fulfilled my wishes, so I figured why not just learn a bit more and code one myself.
Only been coding on the container right now, so here's a little preview.
Basic usage of insert into a table:
use Siberia\Database\DB;
// Select the table...
Exactly, you can easily disable features to minimize dependency loading time amongst other stuff, especially in Laravel.
To be honest, he would be better off using the finished version of my framework.
Yeah true, but yet you're filling the CMS with components used in a framework, which in the end, would make more sense to already use an existing framework.
"filp/whoops": "~2.1",
"patricklouys/http": "~1.4",
"nikic/fast-route": "^1.2",
"rdlowrey/auryn": "^1.4",
"twig/twig": "^2.2"...
To be honest, your back-end looks a little sketchy.
I don't really like the way you're handling routes.
But all in all, you'd better off using an existing framework when I'm looking at the packages you're already using:
Anyway, good luck with this!