Frontend frameworks are great - until they’re not.

React, Vue, Svelte, Solid... they’re powerful, but also heavy, complex, and full of abstraction. What if you just said “no” to all of it?

What if you went framework-free?

🧪 What Is "the Platform"?

When people say “just use the platform,” they mean:

  • HTML
  • CSS
  • JavaScript (vanilla, not bundler-fried)
  • Web APIs like fetch(), FormData, URLSearchParams, localStorage, etc.
  • Native browser features like ,
    , and
    (yes, it still works)

It’s everything your browser gives you out of the box. And spoiler: it's a lot more than you think.

💡 What Can You Actually Build?

Surprisingly... a lot.

  • Static sites? Easy. Just use HTML + CSS.
  • Blogs? Markdown + a build script. No need for a JS runtime.
  • Forms? Native HTML + progressive enhancement.
  • APIs? Call them with fetch(), render with innerHTML.
  • Stateful UIs? EventListener, dataset, classList.toggle(). That’s it.

Unless you’re building a single-page app with dynamic routing, real-time updates, and client-side caching, you might not need a framework.

🧨 Why Bother?

Because:

  • Your bundle size drops to zero.
  • No dependencies = no supply chain drama.
  • No framework = no updates, no breaking changes.
  • It’s fast. Stupid fast.
  • You relearn how the web actually works.

The platform is getting better all the time. Modern HTML is not your grandpa’s

-ridden nightmare. Native forms, popovers, animations, and even transitions are finally decent.

🧱 Where It Starts to Hurt

Let’s be real, going raw has its limits:

  • No routing.
  • No component model (unless you write your own or use Web Components).
  • State management? Manual.
  • DX? Brutal. You’ll miss hot reloading, error overlays, dev tools.

For anything complex or long-lived, you’ll start reinventing wheels fast. That’s when a micro-library or lightweight tool makes sense (think: htmx, Alpine.js, Lit, Petite Vue, etc).

✅ So… How Far Can You Really Get?

Pretty damn far - if you design around the platform, not against it.

The sweet spot:

  • Content-heavy pages
  • Forms and interactions
  • Small apps that don’t justify React

You’ll write less, ship less, debug less, and load way faster.

Frameworks are tools. Not laws of nature. Sometimes the best dev experience… is just the browser.