Why I chose Vanilla JavaScript over React for a production SaaS tool — and would do it again

When I started building Aservus — a free PDF toolkit at aservus.com — the first decision I made was to use zero JavaScript frameworks. No React. No Vue. No Svelte. Pure HTML, CSS, and Vanilla JavaScript. Every developer I mentioned this to had the same reaction: "Why would you do that for a production tool?" Here is my honest answer. The use case made frameworks unnecessary Aservus is a collection of single-purpose tool pages. Each page does one thing — merge PDFs, compress a PDF, convert PDF to Word. There is no complex shared state across components. There is no real-time data syncing. There is no authentication flow with dozens of conditional UI states. The use case that frameworks solve brilliantly — complex, stateful, interactive applications — was not my use case. My use case was: user arrives, user selects file, tool processes file, user downloads result. A framework would have added complexity without solving any problem I actually had. Performance was non-negotiable PDF tools