(04-28-2016, 04:07 AM)dmyers Wrote: How would you compare them speed and memory wise? I know of another framework which adds a ton of "great features" automagically for you (in some cases even if you don't need them they are loaded) Unfortunately, the added extra automagic made it very slow and a memory hog in a real word high volume environment. Now they are adding on even more code to find all kinds of way's to speed it up and work around code.
One reason I personally enjoy using CI is that I start small and fast and build/add on what I need. Instead of getting all kinds of "extras" and then trying to work around and turn off the ones I don't need.
DMyers
The company I'm working for right now is currently using Laravel 5, and I've used Laravel 4 in the past on a few projects. There's no contest in the speed/memory department. CI blows it away in that department. I typically see 10-20ms startup times for CI3 on my dev box. I started up an L5 project yesterday in the day job, and it was seeing 400ms startup times. I don't believe they had much extra in their starting project, either. I'm know Laravel provides some optimization tools, and I'm pretty sure that was running without the optimization. Still, that's a crazy boot up time. I didn't pay attention to memory usage. Will probably look at that today, though.
And, especially with 5, there are lots of little "special features" that are built into things, especially the Eloquent models, that could be done by the user without a special mechanism in place to handle it. I think L4 was a decent framework, but, to me, L5 has jumped the shark and is starting to become too bloated and complex. Taylor's .NET roots are starting to really show, I believe.
To me, the power it has out of the gate, like the Blade templates and the Eloquent model, are offset by the complexity of everything else. It seems easy to use, but that definitely comes at a large price to understand and expand it. Even then, I look at the Collections that Eloquent returns, and realize that he built in all of the features of an array, when an array probably would have covered 90% of what he built into it.
The more I use Laravel, the more I realize just how big a fan I am of explicit code, and much less "magic" behind the scenes. Man, I'm ready for CI4 to be done and production ready
