Well, these are things that show what makes laravel different with others:
1. Bundles are Laravel’s modular packaging system. The Laravel Bundle Repository is already populated with quite a few features that can be easily added to your application. You can either download a bundle repository to your bundles directory or use the “Artisan” command-line tool to automatically install them.
2. The Eloquent ORM is the most advanced PHP ActiveRecord implementation available. With the capacity to easily apply constraints to both relationships and nested eager-loading you’ll have complete control over your data with all of the conveniences of ActiveRecord. Eloquent natively supports all of the methods from Laravel’s Fluent query-builder.
3.Application Logic can be implemented within your application either using controllers (which many web-developers are already familiar with) or directly into route declarations using syntax similar to the Sinatra framework. Laravel is designed with the philosophy of giving a developer the flexibility that they need to create everything from very small sites to massive enterprise applications.
4.Reverse Routing allows you to create links to named routes. When creating links just use the route’s name and Laravel will automatically insert the correct URI. This allows you to change your routes at a later time and Laravel will update all of the relevant links site-wide.
5.Restful Controllers are an optional way to separate your GET and POST request logic. In a login example your controller’s get_login() action would serve up the form and your controller’s post_login() action would accept the posted form, validate, and either redirect to the login form with an error message or redirect your user to their dashboard.
6. Class Auto Loading keeps you from having to maintain an autoloader configuration and from loading unnecessary components when they won’t be used. Want to use a library or model? Don’t bother loading it, just use it. Laravel will handle the rest.
7.View Composers are blocks of code that can be run when a view is loaded. A good example of this would be a blog side-navigation view that contains a list of random blog posts. Your composer would contain the logic to load the blog posts so that all you have to do is load the view and it’s all ready for you. This keeps you from having to make sure that your controllers load the a bunch of data from your models for views that are unrelated to that method’s page content.
8.The IoC container (Inversion of Control) gives you a method for generating new objects and optionally instantiating and referencing singletons. IoC means that you’ll rarely ever need to bootstrap any external libraries. It also means that you can access these objects from anywhere in your code without needing to deal with an inflexible monolithic structure.
9. Migrations are version control for your database schemas and they are directly integrated into Laravel. You can both generate and run migrations using the “Artisan” command-line utility. Once another member makes schema changes you can update your local copy from the repository and run migrations. Now you’re up to date, too!
10.Unit-Testing is an important part of Laravel. Laravel itself sports hundreds of tests to help ensure that new changes don’t unexpectedly break anything. This is one of the reasons why Laravel is widely considered to have some of the most stable releases in the industry. Laravel also makes it easy for you to write unit-tests for your own code. You can then run tests with the “Artisan” command-line utility.
11. Automatic Pagination prevents your application logic from being cluttered up with a bunch of pagination configuration. Instead of pulling in the current page, getting a count of db records, and selected your data using a limit/offset just call ‘paginate’ and tell Laravel where to output the paging links in your view. Laravel automatically does the rest. Laravel’s pagination system was designed to be easy to implement and easy to change. It’s also important to note that just because Laravel can handle these things automatically doesn’t mean that you can’t call and configure these systems manually if you prefer.
Source : http://laravel.com/docs