Skip to main content

PHP Isn't Dead

PHP gets dismissed in every tech stack conversation. But it handles 77% of the web, powers the systems enterprises actually rely on, and keeps shipping.
20 February 2023·6 min read
Hassan Nawaz
Hassan Nawaz
Senior Developer
engineeringdelivery
Every few months someone publishes a post about PHP being dead. I've been building enterprise software in PHP for over a decade, and those posts have been appearing for roughly the same amount of time. Meanwhile, PHP runs about 77% of all websites with a known server-side language. The corpse is doing pretty well.

Key Points

  • PHP powers approximately 77% of websites with a known server-side language, according to W3Techs
  • Laravel has become a mature, full-featured framework that handles enterprise-grade requirements out of the box
  • The "PHP is dead" argument comes mostly from developers who haven't written PHP since version 5
  • Enterprise clients care about reliability, maintainability, and delivery speed - not Twitter discourse

The Numbers

W3Techs tracks server-side language usage across the web. As of early 2023, PHP sits at 77.4%. Python is at 1.4%. Ruby is under 1%. These aren't opinion numbers. They're measured from actual websites.
WordPress accounts for a chunk of that, sure. But WordPress itself powers over 40% of the web, and dismissing PHP because WordPress uses it is like dismissing JavaScript because it runs banner ads. The tool isn't defined by its worst use case.
77.4%
of websites with a known server-side language run PHP
Source: W3Techs, February 2023

What I Actually Build

I've spent years building enterprise systems in Laravel. Portal applications for organisations managing hundreds of users. eCommerce platforms processing real transactions. Management software handling complex business workflows. None of these projects failed because of PHP. The ones that had problems had problems because of scope, requirements, or architecture decisions - same as any other language.
I've never had a client tell me they lost revenue because we used PHP. I've had clients tell me they lost revenue because the previous agency over-scoped, under-delivered, and chose a trendy stack nobody on the team actually knew.
Hassan Nawaz
Senior Developer
Laravel gives me queues, caching, authentication, an ORM, migrations, scheduling, and a testing framework. All built in. All well-documented. All proven across thousands of production applications. When I start a new enterprise project, I'm not wiring together fifteen packages hoping they play nicely. I'm writing business logic on day one.

Modern PHP Is a Different Language

Most of the "PHP is dead" crowd is reacting to PHP 4 or 5. They remember mysql_query(), spaghetti code, and $_GET everywhere. Fair. That was rough.
PHP 8.1 and 8.2 have enums, named arguments, match expressions, fibers, readonly properties, intersection types, and first-class callable syntax. The type system is genuinely useful now. Static analysis tools like PHPStan catch errors before runtime. The language has grown up.
I don't need to convince anyone that PHP is elegant. It doesn't need to be. It needs to be productive, reliable, and maintainable. It is.

The Enterprise Reality

Enterprise clients don't pick technology based on Hacker News sentiment. They pick it based on:
Can we hire for it? PHP developers are available. Not every senior dev wants to work in PHP, but there's a deep talent pool, especially for Laravel. Try hiring a senior Elixir developer in Auckland.
Can we maintain it? A Laravel application follows conventions that any Laravel developer can read. The framework enforces structure. That matters when the original team moves on and a new team takes over maintenance.
Does it integrate? Enterprise systems connect to payment gateways, CRMs, ERPs, government APIs, and legacy databases. PHP has mature libraries for all of this. Most enterprise APIs were built assuming their consumers would be PHP or Java.
Will it be around in five years? PHP has been around for 28 years. Laravel has been around for 12. The ecosystem isn't going anywhere. The same can't be said for every JavaScript framework that launched last quarter.

What Actually Kills Projects

In my experience, projects fail because of bad architecture, unclear requirements, or teams that don't communicate. The language is almost never the problem.
I've seen beautifully architected PHP applications that run flawlessly for years. I've also seen Node.js projects that were rewritten twice in eighteen months because the original architecture couldn't handle production load. The technology choice mattered far less than the engineering decisions made within that choice.
The PHP-is-dead conversation is a distraction. The real questions are: does your team know the stack? Is the architecture sound? Can the system be maintained? If the answers are yes, ship it. Nobody's users care what language the backend is written in.
If you're planning an enterprise build and want a team that picks technology based on fit, not fashion, get in touch.