← All insights

The case for Laravel over Symfony, written by someone who’s shipped both.

What the framework-fight discourse gets right, and what it gets very wrong.

I shipped my first Symfony app in 2014 and my first Laravel app in 2015. I've built production systems on both, including a couple where we migrated from one to the other. So this is a practitioner take, not a hot take.

Laravel wins on developer-velocity for product-oriented work, full stop. The cost of that velocity is a culture of magic — a lot of behaviour you have to memorise rather than read. For 80% of the apps we build, that trade is worth it.

Symfony wins when the team is large, the system is long-lived, and the contract-clarity of explicit configuration matters more than shipping speed. Most of our enterprise rescue work that started on Symfony rightly stays on Symfony.

The framework-war discourse misses the actual variable: team size and longevity. Pick the one your team can read in five years.

Working on something like this?

Let's talk.

A real engineer reads every message. Usually within a few business hours.