Skip to content

← Writing

engineering

Laravel 6: Semver, Ignition, and Growing Up

· Jerwin Arnado

Archive note: this is a backdated post, written years later while rebuilding this site. It’s dated to the moment it covers, but the hindsight is real.

Laravel 6 shipped on September 3, and the most important feature is the number itself. After half a decade of 5.x releases (5.5, 5.6, 5.7, 5.8 — each a “minor” version that regularly required real upgrade work), the framework adopts semantic versioning: major.minor.patch, meaning what they say. Breaking changes get a major number; everything else doesn’t. Paired with an LTS designation, the message is aimed squarely at people like me who maintain client apps for years: upgrades will now be honest about their cost.

That’s the headline for working developers. The rest of the release earns its keep too:

Ignition: the error page you’ll actually see the most

Think about which framework UI you stare at most. It’s not the welcome page — it’s the error screen. Laravel 6 replaces the venerable Whoops page with Ignition: stack traces with editable context, solutions suggested for common mistakes (“did you forget to run migrations?” with a button that runs them), docs links, and a sharing tool for asking colleagues for help. Investing this much polish in the failure experience is a very specific philosophy — the same one that made artisan messages friendly — and it’s exactly the philosophy that wins developer loyalty. You learn a framework through its errors; Laravel just made its errors teach.

Lazy collections: the sleeper feature

LazyCollection brings PHP generators into the collection API you already know: process a million-row table or a multi-gig log file through ->map()->filter() chains while holding one item in memory at a time.

LazyCollection::make(function () {
    $handle = fopen('huge.log', 'r');
    while (($line = fgets($handle)) !== false) {
        yield $line;
    }
})->filter(fn ($line) => str_contains($line, 'ERROR'))
  ->each(fn ($line) => /* ... */);

Every Laravel dev has a war story about User::all() on a table that grew. cursor() now returning lazy collections turns a whole category of memory exhaustion incidents into a non-event. Unsexy, vital.

The rest of the ledger

  • Job middleware — rate-limiting and wrapping logic for queued jobs without polluting the job class.
  • Frontend scaffolding moves out to a laravel/ui package: the framework core quietly admits the frontend is its own world, choose your own adventure. (Filed for future reference; framework-frontend relations feel like a story that isn’t finished.)
  • Free Laravel Vapor compatibility, naturally — the serverless push from July and this release are clearly the same maturity arc.

The arc, named

Stand back and the 2019 picture composes itself: semver for predictable maintenance, LTS for long-lived apps, a first-party deployment platform, errors that teach, primitives for large data. None of these are demo-day features. All of them are operating features — the concerns of people who run Laravel in production for years, which is what the framework’s audience has become. PHP’s ecosystem keeps quietly professionalizing while the wider industry isn’t watching (next up: PHP 7.4 in November — typed properties, finally).

Some frameworks age into legacy. This one appears to be aging into infrastructure. As someone whose livelihood rides on that bet, version 6 reads like the bet paying off.