Skip to content
Try the admin demo 0
In plain words

No framework: what that buys, and what it costs

Most PHP sites are built on a framework. This one is not, and the reason is worth stating honestly — including the part that is a disadvantage.

What a framework is

A framework — Laravel and Symfony are the well-known ones — is a large ready-made skeleton. It answers a thousand questions before you ask them: how a request is routed, how the database is reached, how a form is checked. You write your part inside its shape.

They are good pieces of engineering and a great many fine sites are built on them. This is not an argument that they are bad.

What doing without one buys

Fewer moving parts. You are not carrying several hundred thousand lines somebody else wrote, the vast majority of which your site never uses.

A hole in it is not a hole in you. When a framework has a security flaw, every site on it has that flaw the same morning, and the world knows exactly which sites those are.

Upgrades happen on your schedule. A framework's major version arrives when it arrives, and following it can mean rewriting work that was finished and paid for.

The code can be read. When something behaves oddly, there is a file that does that thing and it can be opened. That sounds small until the day it matters.

What it costs, which is a real cost

More is written by hand. A framework hands you sessions, validation, queues and a hundred other things already solved; without one, each is somebody's work and somebody's responsibility.

And there is no vast shop of ready packages to drop in. That is the trade this CMS makes deliberately: a smaller thing that is wholly understood, instead of a larger one that is mostly inherited.

What this means for your site

  • Nothing to upgrade because a framework decided its time had come.
  • A published flaw in a popular framework is not automatically a flaw in your site.
  • The cost, stated plainly: features that a framework gives away are built here instead.