Do You Really Need That Framework?

Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.

We live in a funny era. Ask for a simple website, and you'll likely receive a mountain of complexity. Frameworks stacked on libraries, tangled in buzzwords and dependencies. But when did "simple" become synonymous with "primitive"?

Stop and ask yourself - just because you can, does it mean you should? This chain of thought more often than not ends with the following question: Why complicate things when you don’t have to?

The Seduction of Complexity

Complexity is tempting. It feels advanced, impressive even. It's thrilling to developers who thrive on solving intricate puzzles, and appealing to businesses dazzled by the apparent sophistication. However, when you take a step back and look again, you realize complexity is often self serving.

Does a bakery's website truly need a React app with server side rendering? Does your web shop genuinely benefit from a full GraphQL layer? Probably not.

The Beauty of Simplicity

"Simple" is not a dirty word. It never should have been, that is. We made it that way. In reality, "simple" is efficient, elegant, and at its very core, user friendly. A website built from plain HTML, CSS, and a bit of JavaScript is just... logical.

Such simplicity means:

• Pages load instantly
• Lower costs for development and hosting
• Easier maintenance and updates
• Fewer security risks

Funnily enough, simpler sites often outperform their more complex counterparts. Faster load times keep visitors happier and boost conversions. Clear interfaces prevent users from wandering off in confusion. A simple website does exactly what it needs to, and nothing more.

"Static" Doesn’t Mean Stale

People hear "static" and think of forgotten relics from the early web days. But long gone are the days of struggling with the ways we used to make them. Nowadays, static sites are agile, quick, and incredibly effective. Tools like Astro, Hugo, or Eleventy bridge the gap between minimalism and modern convenience without dragging along the unnecessary baggage of complicated tech stacks.

And even without these tools, there’s something beautifully liberating about plain old HTML, CSS, and JavaScript files. They're pure. They're fast. They're just simply good. They're like a cheeseburger with fries. Beef Wellington is great and all, but come on, we're talking about cheeseburgers here.

"Complex" Doesn't Mean Good

Tools have to be chosen deliberately, never because they’re shiny or popular. They have to be chosen because they’re right. Every choice we make must be guided by, at the very least, one simple criterion: Does it help the end user?

Sure, frameworks have their place. Complex web applications, rich interactivity, personalized user experiences, but they're not a default solution. Maybe tech stacks should be approached with Occam's razor in mind - the simplest explanation (or tech stack, in this case) is the best one to follow.

So What's the Deal with Modern Static Site Generators?

If you're wondering exactly how these modern static site generators work, here’s a quick rundown:

• Astro: Astro allows you to use frontend frameworks like React, Vue, and Svelte but only compiles the minimal necessary JS to HTML and CSS. Your components become static web pages, reducing load times drastically. It's perfect if you love components but hate slow load times.

• Hugo: Hugo is fast. Like, really, really fast. It uses markdown or JSON/YAML files for content, generates clean HTML/CSS during a build step, and provides a pretty cool templating language. It’s best for large, content driven websites or blogs that need regular, straightforward updates.

• Eleventy (11ty): Eleventy is delightfully simple. It uses plain HTML templates or popular template languages like Nunjucks, Markdown, or Liquid. Content is typically managed via simple markdown or data files. Eleventy generates clean HTML/CSS with virtually no JavaScript overhead by default.

From a workflow perspective, here's what you usually do:

1. Write your content in markdown, JSON, or plain HTML files.
2. Build your templates and components with your preferred templating language or simple HTML.
3. Run a build step, where your content and templates compile into plain HTML, CSS, and minimal JavaScript files.
4. Deploy the static output to any hosting service like CDNs, Netlify, Vercel, GitHub Pages, or even a simple FTP server.

Super simple.

Honesty

As Galadriel famously said, the world is changed. Clients are tired of waiting, tired of confusing meetings, tired of technical mumbojumbo and tired of complexity for complexity's sake. They want clarity. They want things to "just work."

Embracing simplicity is about honesty. It's about you, as a developer, respecting your client's time, and them, in turn, respecting their users' time, patience, and experience. It's about having the courage to say "no" when everyone else is saying "yes."

Before your next web project, pause and ask yourself sincerely: "Do I really need that framework?"

Your clients and their users might thank you more than you imagine.