When comparing Inkscape vs Laravel 5, the Slant community recommends Inkscape for most people. In the question“What are the best web design tools?” Inkscape is ranked 10th while Laravel 5 is ranked 11th. The most important reason people chose Inkscape is:
Inkscape is GPL-licensed and maintains public repositories.
Ranked in these QuestionsQuestion Ranking
Pro Free and open source
Inkscape is GPL-licensed and maintains public repositories.
Pro Opens lots of file types
Inkscape supports many common formats for import (including SVG, Photoshop and Illustrator) and its plugin architecture allows more to be added.
Pre-built binaries are available for Windows, Mac and Linux. Inkscape can be built from source on additional platforms.
Pro Export to different file types
You can export and save your files for example as a "normal" svg, png, jpg, bmp etc. file.
Pro Integrates well into a X11-System
Its uses the X11 icon theme and desktop theme(GTK).
Pro Dark Theme Support
The new 1.0 beta 2 version finally got support for dark theme which normally is only available for commercial software like Affinity Serif, Adobe Illustrator.
Pro Measurement Tool
This tool is extremely handy and I was not able to find it in any other vector graphics programs out there.
Pro Live Path Effects
Extremely powerful menu that offers more than 30 powerful Live Path Effects to apply to your paths vastly enhancing the application functionality.
Pro Guides, Grids, and Canvas Rotation
Extremely handy features when building complex graphics using Inkscape.
Pro Interface is available in 29 languages
Basque, British English, Brazilian, Portuguese, Catalan, Croatian, Czech, Dutch, Finnish, French, German, Greek, Hindi, Hungarian, Icelandic, Indonesian, Italian, Korean, Latvian, Norwegian (Bokmål), Polish, Romanian, Russian, Slovak, Spanish, Swedish, Turkish, Ukrainian, Urdu, Swedish.
Pro It can do anything
A very powerful software that can do pretty match anything!
Pro It's really easy and fun
You can edit and create vector graphics with Inkscape.
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 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 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 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 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
Con Very slow startup on some systems
Depending on factors like how many fonts you have installed, Inkscape can take upwards of 30 seconds to launch.
Con Uses its own SVG-format by default
Inkscape might use SVG as its default format, however this SVG's contains some additional SodiPodi/Inkscape additions that can be troublesome if you want to import the SVG into some other application.
Con Based on the GTK widget toolkit
Software is based on GTK, so it might not integrate well in non-GTK environments. It also requires many dependencies on those non-GTK desktops. It also adds dependencies to GTK-environments since it is written in C++ which requires the gtkmm wrapper/interface
Con Mac version does not look as polished as its versions for Windows/Linux version for the 0.92.x version.
It seems that Inkscape 1.0 beta 2 for Mac got some needed attention and it looks a lot better with dark theme support. native DMG installer and they got rid of X11 which is great.
Con Incompatible with previous versions
Sometimes backward compatibility breaks. For example, pre 0.92 SVGs are incompatible with later releases (due different default resolutions).
Application is often buggy so it happens from time to time that the popup / right-click menu won't close and stays open. It crashes also sometimes randomly. This makes it almost unusable for productive / business use.
Con Y-axis inverted
0,0 coordinates begin in lower left corner, not upper left corner as SVG standards define in Inkscape 0.92.x.
It seems this is now fixed in the 1.0 beta 2 version of the program.
Con No support for large printing machine system
No support for large printing machine environment, except exporting the resulting artwork to PDF.
Con Since 0.91 the gradient editor is gone
It is now only possible to edit a gradient on screen. but you can't set a stop to a specific percentage anymore.
Con Limited work with ICC CMYK color scheme
Support for ICC color profiles only in SVG files.
Con Crashes very often
Inkscape encountered an internal error and will close now - is one of its standard messages.
Con 1.0 is sluggish
Inkscape 1.0 uses GTK 3 which is sluggish and slow even compared to previous versions.
Con Uses too much magic methods
It complicates debugging and autocompletion.
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.