Symphony is much more challenging to learn and requires a longer development cycle than Laravel. Django is a Python framework similar to Laravel, but it is very opinionated. Everything must be done the Django way, and it is a bit more restrictive than Laravel. It does have a …
Laravel's community was more active, the ecosystem was more expansive, and the documentation was much stronger. CakePHP caught my eye for its simplicity; however, when I began exploring all of the things that I hoped that the web application might be able to do, it quickly …
Laravel PHP Framework's documentation and toolchain sets it above the rest by making it easy to work into your environment. Spend more time creating and less time configuring servers.
WordPress with WooCommerce provides the good support for WooCommerce but as it is built on top of the WordPress limitations kick in whereas we can build whatever we want using Laravel PHP Framework. Laravel PHP Framework and WordPress is open source whereas Shopify is not and …
I have used CodeIgniter in the past for a couple of projects. As per my experience, we can go for CodeIgniter for smaller projects due to its simplicity. But as the project size grows, one should choose a more organized framework with larger community support. This is the …
The majority of the above-mentioned frameworks are good at some particular things. Laravel PHP Framework in general is capable of doing all the same things with standard best practices. Additionally, Laravel PHP Framework brings great community support that is ever-growing. the …
Laravel is much better than CodeIgniter in many aspects, First of all it is more secure and robust. It has a great troubleshooting mechanism. They have added more libraries, themes and plug-ins for different purposes. The MVC model helped the developers to get rid of writing …
Both frameworks, by in large, serve the same needs and are only dependent upon the platform that will be supported. However, I find .Net to be a bit more robust when it comes to data security needs (encryption, management, etc.) compared to Laravel and that may be a deciding …
Originally, it was a decision between Zend, CodeIgniter, and CakePHP for me. I chose CakePHP and used it as my main PHP framework for at least a couple of years before noticing and giving Laravel a fair try. Ultimately I selected Laravel because I felt it fit with my preferred …
Laravel PHP Framework is the most developed, updated framework right now, with lots of features. Using older versions is less appreciated by the developer community. It is well documented, and Laravel has a pretty big community of supporters getting your query solved faster and …
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you …
If you are using PHP, you should be using Laravel! It is superior in every way to CodeIgniter & CakePHP. Not to be unfair to Cake & CodeIgniter, which both have built in ORM, making queries very simple. Laravel on the other hand offers their eloquent ORM that makes database …
Laravel PHP Framework is continuously updating its framework and developing new tools to make web development more useful, optimized, and bug-free. Also there is a large community of users on Stack Overflow and other websites that can help you get questions cleared up quickly. …
When we were using CodeIgniter, it always felt that something is missing. We were unable to find the proper libraries that supports it and the support from the community around. Once we came to know about Laravel, we never have touched CodeIgniter. Laravel is a well documented …
Laravel is built on top of Symfony so is naturally a better upgrade. It is far superior than cake and igniter (in my opinion). I don't remember, but somewhere in internet someone made a comparison with Laravel and others as racing motor-bike vs a cycle. Because of large …
I inherited Laravel projects originally created by other developers. I haven't migrated clients at this time, however as the project gets bigger and I need to find more elaborate workarounds to address needs that option will be put on the table.
The best comparison I can make is against Symfony. It's curious that Laravel is built on top of Symfony. They chose the packages that they found to be useful. Symfony for instance comes with way too much stuff that in the end you never use, and Laravel just comes with the right …
I would say that Laravel is not a suitable framework for high-frequency, high-volume, real-time interaction or processing millions of records in batch operations. It shines for standard database web applications (CRUD, Admin Panels, etc.) and is a fantastic multi-developer framework.
Laravel utilizes the best possible PHP standards and coding practices.
Laravel uses many widely-accepted community libraries and builds upon them, rather than re-inventing everything.
Laravel has many components available from the community and is extremely easy to build custom components for, either with custom code or by integrating existing third-party PHP libraries.
Laravel is flexible enough to power pretty much any kind of application I can imagine.
Laravel is updated regularly, which is great. However, in order to get the latest features, use the newest 3rd party libraries, have the most current security updates, and ensure that the newest features of PHP are usable, you have to continuously upgrade your Laravel application. This costs time and money, obviously, and if you don't stay on top of the updates you will quickly fall behind. This is the case with any open source software, but it needs to be considered for any team considering using Laravel or any other software.
Because of the size of the Laravel community, there are a LOT of 3rd party libraries. Some of these are great, some are less than great. Sometimes it's difficult to evaluate the quality of a library, making it difficult to trust many libraries. Developers need to be cautious and thoughtful when considering using new software.
Because of the rapid development of the Laravel framework, the size of the community, and the simplicity of being able to publish content online - it is very easy to find documentation, tutorials, or other "advice" that is not up to date, or that has outdated information.
Laravel PHP Framework has continued to exceed my expectations. It supported me in the development of a high quality and stable web application that is mission critical for the organization. I cannot imagine wanting to use any other tool for web development. Documentation, unit tests, and numerous integration options make using Laravel PHP Framework a natural choice.
As I mentioned earlier Laravel PHP Framework has lot of in built feature as well as there is vast set of packages available to add the features in your application. It has very large community who can help when you feel stuck somewhere. This is why this rating is justified.
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you if you have problems. Using Laravel, integration became easy with third-party libraries, but it was costly too.