March 24, 2026
No‑build? No chill!
No-build, no-NPM, SSR-first JavaScript framework if you hate React, love HTML
HTML purists cheer, React loyalists groan — the no‑build brawl is on
TLDR: Qite.js pitches a back-to-basics web: server-rendered pages, no build tools, and HTML as the boss. The crowd is split between cheering simplicity and blasting the “hate React” vibe, with debates over inevitability of tooling and comparisons to htmx/Alpine lighting up the comments — and that’s why it matters.
Qite.js just slid into the chat promising a simpler web: no build tools, no npm installs, and no make-believe browser in memory — just HTML, real pages, and sprinkles of JavaScript. Think of it as a breakup letter to heavy frameworks like React: render on the server, enhance on the client, keep the page as the truth. And the internet immediately turned it into a street fight.
The bold tagline — “if you hate React” — set the tone. Critics called it a bad look, with one reader firing, “you shouldn’t make ‘hate’ part of your tagline.” Others argued Qite is cute for small-to-medium sites, but not “real apps.” Meanwhile, pragmatists piled on with, “build steps are inevitable,” pushing alternatives like Web Components plus a reactive “signals” library. Even semantics got spicy: someone asked why the demo used a div pretending to be a form, which sent HTML purists clutching their pearls.
Still, Qite got love for its clean “fields/flags” state rules and a vibe that feels closer to htmx and Alpine.js — both popular for no-build setups — prompting the big question: why a new framework instead of building on those? The dev’s pitch: treat the page as the source of truth and skip the rerender circus. Whether it scales to large Single‑Page Apps (aka SPA) is the cliffhanger. For now, the comments read like a reality show: Team Keep-It-Simple vs Team Tooling Forever, with a side of SSR drama and meme-ready “div cosplaying as form” jokes.
Key Points
- •Qite.js is a no-build, no-npm JavaScript framework that runs directly in the browser with plain JS modules.
- •It is DOM-first and avoids a virtual DOM, diffing, and synthetic re-render cycles by manipulating the real DOM.
- •The framework is SSR-first, attaching behavior to server-rendered HTML, with optional SPA capabilities for sections or entire apps.
- •Qite maintains separation of concerns: HTML for markup, JavaScript for behavior, and CSS for styling, supporting standard CSS animations.
- •It introduces declarative state rules based on fields and flags, and a component model where children emit events and parents make decisions.