When comparing Light Table vs Laravel 5, the Slant community recommends Light Table for most people. In the question“What are the languages that have most powerful and easy to use free IDEs?” Light Table is ranked 10th while Laravel 5 is ranked 12th. The most important reason people chose Light Table is:
With LT's inline evaluation, you don't have to re-compile your whole source file. Each time you want to see an output, all you have to do is hover your cursor over the line you'd like to evaluate and press `ctrl+enter`; LT will evaluate that line of code for you.
Ranked in these QuestionsQuestion Ranking
Pro Inline evaluation
With LT's inline evaluation, you don't have to re-compile your whole source file. Each time you want to see an output, all you have to do is hover your cursor over the line you'd like to evaluate and press
ctrl+enter; LT will evaluate that line of code for you.
Pro Your code runs live as you write it
The "Watches" feature lets you see your code running live as you type it. This means that you can debug your code live while writing it, which leads to considerably less programming errors.
Pro Plugin manager available
LT has a plugin manager built directly inside of it. This plugin manager connects to LT's own registry of plugins, so whenever you want assistance while writing your HTML, JS, or even Python, just open up the plugin manager, search for it, and click the little install button beside it's name. Your plugin will then be installed.
Pro Comes with an excellent built-in ORM
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.
Pro Comes with its own CLI
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.
Pro Good for building RESTful APIs
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.
Pro Good documentation
Laravel's documentation is thorough and very good. It covers everything and is very helpful to experienced and new users alike.
Pro Easy to write web apps with authentication
Laravel comes with Authentication capabilities and a fully-powered Auth class out of the box. For passwords it uses bcrypt.
Pro Can use Symfony components
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.
Pro Handles event queuing
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.
Pro Gives developers a great degree of freedom in how they set up their project structure
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.
Pro Gulp tasks in the form of Laravel Elixir
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.
Pro Easy to learn
Pro Extremely powerful template system
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.
While the speed doesn't seem to be an issue with it (on local tests), in production it may be hindered. The framework creates a ton of files and folders, some of which your app might not even use. Not good if you don't like having a ton of folders and rigid non-standard PHP folder structure for development.
Con Uses too much magic methods
It complicates debugging and autocompletion.
Con Hard to use model properties
You need to check all model properties in database to know it exists, or declare all them manually.
Con Steep learning curve
While a lot of times you can write things in plain PHP, it will hinder you down the line when you want to use core features and find that you have to rewrite code which then causes issues throughout the app. Documentation is good, but you need to know what you are looking for and practical examples are non-existent. Many features have been updated throughout the versions in such a short time that tutorials you find online are confusing to sort through outdated tutorials and guides that no longer work or have been depreciated.
Con Follows bad design practices
Uses bad practices, like Singletons, Magic models, Middleware.