PHP
Why We Still Ship Procedural PHP in 2026
Published May 2, 2026
Every few years a new abstraction promises to make backend work disappear. Routers, ORMs, service containers — each one buys convenience by hiding the request/response cycle behind a wall of configuration.
Procedural PHP refuses that trade. A request comes in, a script runs top to bottom, and every line is visible in the file you are looking at. For small-to-medium applications — the overwhelming majority of what gets built — that visibility is worth more than the boilerplate a framework saves you.
What you get back
- No hidden middleware chains to trace through
- No magic method resolution — a function call is a function call
- Deploy target is a folder of
.phpfiles and a database, nothing else
This does not mean sloppy code. Prepared statements, CSRF tokens, input validation, and clear separation between includes and route files still apply — they are just explicit instead of implied by a framework contract.
← Back to all articles