I don't know why everyone it is so excited about this framework. I've had a quick look over the documentation a few months ago, when there was this hype around <i>this new kid from the block</i> thinking that there must be something really interesting.<p>I stopped reading the minute I saw they are using a template engine for rendering the views. I simply don't get it. Why would someone use a separate template engine when PHP itself is a very good one to use ? Why to add an extra layer to the app ?<p>We don't have to recreate anything, the views should be pure PHP, not code written in some <insert template engine name here> that is then translated to PHP.
I used Laravel for a small project for the past couple months. Although I started web development in PHP, I am strictly a Ruby/Rails developer right now and I have to say working in Laravel felt very natural and right at home. I'm not saying that being Rails-like is merit in it's own right, but I had that same feeling with Laravel as I did when I first started using Rails. I'd highly recommend trying this framework and hope with more projects we can see some solid documentation grow.
I was heavy on CodeIgniter before and ever since I launched another website with Laravel I don't feel like going back to CI. In fact if I get time I wanted to relaunch my other sites with Laravel. If you closely follow the MVC frameworks and the way they are moving forward Laravel sounds like right on the track which CI lags big time. Give it a serious try and you will know. I got completely hooked with its robust Routing system.