Why CyberScryb Uses Vanilla JS (No Frameworks)
If you build web apps in 2026, everyone expects you to reach for React, Next.js, Vue, or Svelte. Writing raw HTML, CSS, and JavaScript gets you weird looks. But CyberScryb, which has 50 working tools, does not use frameworks. The site runs entirely on native browser APIs.
This article explains the decision, the benefits of native code, and reasons to avoid frameworks in your next project.
Check out our tools and experience the speed for yourself. Our AI Humanizer and calculation utilities load in milliseconds because they run on pure, framework-free JavaScript.
Explore All Tools →The Origin: A CNA's Night Shift Constraints
To understand why CyberScryb is framework-free, you must understand the backstory. The founder worked night shifts as a CNA in a memory care facility. During patient rounds, quiet times, and breaks, the work offered fifteen-minute windows to write code.
Coding on slow devices leaves no time to run package installs or download heavy modules. You want to open a text editor, write a script, refresh the page, and see results. Vanilla JS made rapid building possible in low-resource environments.
Speed is a Product Feature
Modern web users are impatient. A site taking three seconds to load loses traffic. By using native code, we keep page sizes small:
- No Hydration Lag: React apps download a bundle, parse code, and then process the page. CyberScryb calculators run the millisecond the HTML displays.
- Minimal Network Payload: The total script size for most tools stays under 5KB. Framework configurations require much more setup.
- Long-Term Stability: The web platform maintains backward compatibility. A Vanilla JS utility runs for years without compilation problems.
Modern Browser APIs are Incredible
Back in 2012, jQuery and frameworks were necessary because browsers had different, buggy implementations of basic features. In 2026, the modern web standard is highly unified. Browsers natively support:
document.querySelector()anddocument.querySelectorAll()for DOM selection.- Native web components and template literals for reusable UI elements.
- The
fetch()API for asynchronous network requests. - Native CSS variables (Custom Properties) and grid layouts, eliminating CSS preprocessors like Sass.
When the platform does the heavy lifting, you don't need a framework to wrap it.
FAQ
Isn't code organization harder without components?
Sloppy coding causes problems. I organize each tool as a self-contained HTML page with a dedicated script file. Shared utilities live in /tools/shared/. I separate inputs, calculations, and UI updates into functions with clear comments. The organization mirrors React component structure without the abstraction layer.
Do you use any build steps?
A few small ones. A Node.js script generates static pages from templates and builds the sitemap. Everything the browser loads remains plain HTML, CSS, and JS. No webpack, no babel, no transpilation. The output is the source.