Joomla vs Laravel PHP Framework

• Multiple templates assigned on a page-level basis allow fine-grained control of your site design
• Excellent ACL out-of-the-box means you can have a mutli-user website up and running without needing to install anything additional
• Straightforward control panel and useful help features and documentation make it easy for people to manage their own websites

Read full review

• Good ORM along with support for a number of database systems though be prepared to solve some weird issues when dealing with querying relationships between models.
• Deployment is very simple especially if you use Laravel Forge, you can deploy everything at the click of a few buttons.
• Laravel blade templating engine is a very useful templating engine similar to jade in nodejs and it can save a lot of time while writing html logic

Read full review

• Updating was never as seamless/easy as it seems to be with Wordpress. Obviously we accounted for this with our own workflow/methods, but I remember whenever we did WordPress updates it always seemed a breeze compared to the time/energy involved with a Joomla update/upgrade.
• For a while (I think this has changed some) Joomla left itself open to attacks when administrators were not as well versed as they should be. There were developer additions that did security checks/audits for you, but the CMS was the subject of a lot of attacks when left in the hands of our clients for a long time (who had changed permissions to make editing easier/convenient). Ideally the CMS would have been more restrictive on some of these things to prevent easy abuse. Obviously this is more the fault of the misinformed/human then the CMS, but it could have been more dummy-proof.
• No native versioning. There are some community extensions that add this functionality, but they pale in comparison to the versioning plugins of other CMS's (WordPress specifically). Again this was some time ago and in our experience, it could have changed by now.

Read full review

• 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.

Read full review

• Reduces Maintenance Expense - Simple interface saves clients money on site management by allowing inhouse management where desired
• Ease of Updating - Reduces website upgrade expense by allowing template upgrades without the need for redevelopment of content
• Scalability is huge - Client gains entry to an enterprise level web presence with a smaller budget and can grow/add functionality as the budget allows without a redevelopment of the entire site.

Read full review

• Positive: Our delivery time for PHP application is faster than usual.
• Positive: Developers are happy and they write better code with their usual development tools. No tool-upgrade necessary.
• Negative: Initial delivery took 6 months extra and had to rewrite project several times.

Read full review