web2py vs Laravel 5

web2py documentation does not follow the common pattern of using Sphinx, MkDocs or ReadTheDocs which is goos for exeperienced developers. Although documentation in form of a book is very easy and good for beginners. Turning web2py the most easy and comprehensive framework to learn and also to teach.

Web2py apps are designed to be portable. With some minor restrictions web2py apps can run on any VPS on SQL databases and/or Mongo, as well as on Google App Engine with the Google Datastore. It is truly code ones and run everywhere. For example at Camio.com we use web2py internally to access a GAE datastore which contains more images than Instagram.

The web2py community is open and friendly and it gives concrete support to newbies and old timers. It's not difficult to get answers from the BDFL Massimo Di Pierro himself.

One really positive aspect of web2py application is their maintainability over the years. Old code works even if the framework is updated to the latest version. Not only that, if code is written well it is very short and a new team can pick it up over in little time.

While web2py has its own web based IDE which is convenient, it works with WinIDE, PyCharm, and Eclipse. The first two explicitly support web2py. The latter requires some configuration.

web2py is very easy to learn for beginners, yet it has a great deal of power and flexibility as application needs become more complex. It includes an impressively comprehensive set of features, making development very productive without the need to integrate a lot of third-party libraries.

The framework is really fast in production after some optimization and fine tuning which can minimize the memory footprint in order to make it run on a really small VPS or slice.

Allows users to easily extend functionality by using external libraries.

Models and controllers live in the context of the HTTP request. So the developer does not have to import the API to access this context at every request.

In other words, the models, controllers and templates in web2py use a domain specific language which uses pure web2py syntax and allows to import any module but exposes a few additional objects.

web2py includes an "admin" app that serves as a web-based IDE for web2py applications. It includes many features, such as application creation, compiling, and packaging; an error ticketing system; a code editor; a debugger; a controller doctest runner; Git and Mercurial integration; and one-click deployment to PythonAnywhere, Google App Engine, and OpenShift.

It is not intended as a full desktop IDE replacement, but it includes some helpful web2py specific functionality and can be convenient for basic editing and debugging tasks and quick prototyping, even for those who primarily work with a more full-featured desktop IDE or editor.

With migrations, powerful and intuitive Eloquent CRUD, resource routing, and simple JSON response out of the box, a complete REST API can be written in hours.

Laravel's Eloquent ORM is a simple and fast Object-Relational Mapping which helps with organizing the application's database. It supports the most popular databases (MySQL, Postgres, SQLite, etc.) out of the box.

Laravel's documentation is thorough and very good. It covers everything and is very helpful to experienced and new users alike.

Laravel supports event queuing and it does so in a very simple way. To create an event that should be queued just run:

php artisan handler:event SendPurchaseConfirmation --event=PodcastWasPurchased --queued

This creates a handler that implements the Illuminate\Contracts\Queue\ShouldBeQueued interface. Now when this handler is called it will automatically be queued by the event dispatcher.

Laravel comes out of the box with it's own CLI called Artisan. With Artisan developers can do several different tasks such as migrating databases, seeding databases, clearing the cache and much much more.

Laravel comes with Authentication capabilities and a fully-powered Auth class out of the box. For passwords it uses bcrypt.

Laravel allows for free configuration and does not force developers to use a single project structure, instead they can change it to how they wish.

Laravel uses many libraries built for the Symfony PHP framework. Many of these libraries are well-built and have been tested by users before. Since the point of using a web framework is to shorten development time and to avoid reinventing the wheel for problems that have already been solved, then it's logical for a framework to use libraries already built to solve problems that have already been solved.

Laravel has a powerful template system called Blade. It's quite similar to Twig or Moustache with lots of curly braces but the real power comes from the usage of PHP code directly in the view. Blade templates compile directly to raw PHP and are processed in the server when a request is made.

In Laravel 5.0 they added Laravel Elixir, which provides an API for using Gulp tasks for Laravel applications. Elixir supports several CSS preprocessors and even some test tools. But it's still in the early stages of development and it will be developed even further in the following releases. With more methods and more Gulp tasks supported.

Has a great Ecosystem with SAAS like: Forge, Envoyer, Nova & from 3rd parties like oh-dear