Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Laravel 5 vs Krita, the Slant community recommends Krita for most people. In the question“What are the best web design tools?” Krita is ranked 2nd while Laravel 5 is ranked 10th. The most important reason people chose Krita is:
All the most used and useful tools are easy to find in Krita's UI and are often just one click away. They are not hidden behind menus or dropdowns.
Specs
Question Ranking
Pros
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 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 Good documentation
Laravel's documentation is thorough and very good. It covers everything and is very helpful to experienced and new users alike.
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 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 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 Easy to learn
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 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 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.
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 Great Ecosystem
Has a great Ecosystem with SAAS like: Forge, Envoyer, Nova & from 3rd parties like oh-dear
Pro Great Community
Pro Easy to use layout
All the most used and useful tools are easy to find in Krita's UI and are often just one click away. They are not hidden behind menus or dropdowns.
Pro Constantly updated
Krita is getting constant releases with updates and bug fixes. New features are added at a pace that far surpasses the other alternatives.
Pro Free and open source
Krita is completely free and open source. They have raised a couple of successful Kickstarters in the past to get the initial financing and now they are accepting donations.
Pro Developed in part by KDE, which has a great community and therefore great support.
KDE has a long history of making solid applications.
Pro Amazing support for displaying brushes
Krita's preset brushes are one of the default dockers. Each brush has a preview on mouseover that shows a detailed view of the type of brush involved. All the brushes also have useful and descriptive names such as "HP Pencil" or "Textured Fuzzy".
Pro Very customizable
Although the UI is rather busy, Krita is very customizable. The editing window can be themed and the sidebar can be customized extensively throw many dockers or panes.
Pro Easy editing in a tiled view
Tiled view that shows your image tiled in the editor, and permits you to edit it as you are seeing it tiled. If the brush passes out of your texture, it will just automatically wrap back the painting to the other side of the original texture, while permitting you to paint and see the results on any of the tiled "clones" (the shortcut key to activate this is w by default).
Cons
Con Uses too much magic methods
It complicates debugging and autocompletion.
Con Bloated
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 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 Poor performance
Con Follows bad design practices
Uses bad practices, like Singletons, Magic models, Middleware.
Con New features are not tested thoroughly
Since releases are so often and with little time between them, usually new features are not tested a lot and this can bring a lot of bugs with them. Which fortunately are quickly patched in the next release.
Con Documentation is lacking
Krita's official documentation is incomplete in some areas, especially for new features that are constantly added. But this is compensated with it's great design and usability which makes it easier to understand how things work.
Con Poor touch controls
They are still pretty much a WIP. But they are getting there.
Con Working with text is not that pleasant
