Personally I like to follow coding standards when writing app in given framework, so I always start with looking at what they look like and I find that very often there is something that I personally find off e.g. in lavarels case they use tabs for indentation or classes have braces in the same line as class name, but not methods. Other than that project looks great!
I really liked the static method shortcuts Laravel has for almost everything. Too bad it's almost as slow as Symfony, because it uses so many of it's (great) components.
There's also a Laravel 4 book released today. It's Laravel: Code Bright (https://leanpub.com/codebright) by Dayle Rees, a member of the Laravel core team.
It's the featured book on the Leanpub homepage (https://leanpub.com/) right now, and it's doing really well.
Yeah, I forgot to mention https://leanpub.com/laravel-testing-decoded which is an oversight on my part! Laravel 4 is #1 and #2 on Leanpub for the past week, just because of today!
23 comments
[ 2.6 ms ] story [ 50.8 ms ] threadIt has good documentation (available here[0] for version four) and the code is filled with comments if the documentation isn't enough.
It uses "Eloquent ORM" which makes it so easy to handle data with Active Record.
RESTful controllers makes it easy to handle the request.
And much more, which is why you need to read the documentation to understand why it's different.
[0] http://four.laravel.com
Great! I have always ignored that part of the spec. Tabs rule.
I've only made a couple of sites using Laravel but I actually really like it and haven't hit any performance bottlenecks yet.
It's the featured book on the Leanpub homepage (https://leanpub.com/) right now, and it's doing really well.
(Disclosure: Leanpub cofounder here.)