Where a tool sits in the pipeline
Jeremy Keith's split of developer tools into two buckets remains a useful lens, even if neither bucket has a settled name ("Internal and external? Developer-facing and user-facing?"). The first holds things like build tools, version control, transpilers, pre-processors and linters — tooling that runs on your machine or a server and emits the raw materials of the web: HTML, CSS and JavaScript. The second holds tools made of those raw materials, such as CSS frameworks and JavaScript libraries.
The line blurs in practice. Sass belongs firmly to the first category, since it never reaches users directly, yet how you use it shapes the CSS that does — larger or smaller depending on your authoring.
Compiling yourself away
Svelte is the interesting case: it aims to compile as much of itself out as possible before anything ships, leaving some JavaScript but none of the developer-facing API overhead. And it can be pushed further — SvelteKit can disable hydration altogether and pre-render pages, producing a site with no JavaScript, or JavaScript only where you opt in.
The default matters, though. As Jeremy puts it, React can be made to behave like a category-one tool, but that is not its default behaviour, and "default behaviour really, really matters" — React assumes the code you write, and the tooling you write it with, goes over the wire to end users. React Server Components, from the React team itself as SvelteKit is from the Svelte team, hint at change, though widespread adoption looks distant.
Astro and the incumbent's syntax
Astro's pitch, per Jeremy, is that it accepts the same syntax as the incumbent, React, so developers who learned React to get a job needn't learn a new syntax; a full React-to-Astro conversion may not be a single switch, but there's a clear upgrade path.
That claim is demonstrably true. A small serverless microsite was converted from Gatsby (React-based, so its components were already React components) to Astro; the pull request is messy but public. Some of it became .astro files while much of the componentry stayed as .jsx React components largely untouched. React does not ship to users, and JavaScript is almost entirely gone from the site apart from some hand-written vanilla JavaScript for light interactivity.
A developer-facing tool that shrinks the user-facing payload
The coin-flipping feels appropriate here. Astro reads as a developer-facing tool: it uses the Vite compiler, is fast and pleasant to work with (rough edges and all, being pre-1.0, but the DX is largely there), scopes styles, supports SCSS, and lets you write components in many different frameworks. Yet it also helps the user, with no JavaScript bundle on the site at all.
So Astro doesn't redraw the categories — it is developer-facing. It just takes what would be a user-facing tool (even Svelte) and makes it almost entirely developer-facing.



