Web development loves novelty. One framework chases another, one dependency drags in thirty, and two years later the project no longer compiles without updating everything. I have seen many sites die less from wear than from abandonment: one day, nobody dares touch them any more.
Fashion against time
Chasing every new thing means accepting that you will rebuild everything at short intervals. Every fashionable tool is tomorrow’s debt. I say that knowing what I am talking about: I started on Flash, and I saw what becomes of a reigning technology when it disappears. Building to last starts with a refusal, the refusal of the headlong rush. I choose few tools, but tools I know will still be here, and still readable, several years from now.
Standards do not expire
HTML from 2010 still works. So do standard CSS and JavaScript. What breaks is what we stack on top. So I aim at the foundation: static HTML, modern but standard CSS, a minimum of hand-written JavaScript. Fewer dependencies, less debt, fewer reasons for it to fall over. A restrained site is a site that lasts.
Longevity as value for the client
A site that holds ten years without a rebuild is a budget that serves the brand instead of paying for its own reconstruction. It is also a lighter footprint: less computation, less data, less waste. Technical restraint is not an aesthete’s pose. It is common sense, ecological as much as economic.
I do not build for the launch demo. I build for the tenth year, the one nobody is watching any more. It is the same demand as on a board: what counts is holding the line for a long time.
