Javascript

Svelte 5 replaces the old let plus $: reactivity model with runes, a small set of compiler-recognized functions that look like normal JavaScript but get rewritten into fine-grained reactive code. Instead of declaring let count = 0 and hoping the compiler infers a reactive binding, you write let count = $state(0). Instead of $: doubled = count * 2, you write let doubled = $derived(count * 2). Instead of $: console.log(count), you reach for $effect(() => console.log(count)). Props become let { name } = $props().

The short answer: build an interactive data table with semantic HTML (<table>, <thead>, <th scope="col">), add ARIA attributes (aria-sort, aria-live, aria-controls), and wire up keyboard handlers that enable sorting, filtering, and cell-by-cell navigation without a mouse. Done right, the result satisfies WCAG 2.2 Level AA, works for sighted users, screen reader users, and keyboard-only users, and needs no framework dependencies .

This guide walks through the markup, the ARIA attributes, the JavaScript event handlers, and the performance trade-offs you hit once your dataset gets large. The reference patterns come from the WAI-ARIA Authoring Practices Guide sortable table example and the grid pattern .

Picking a React framework in 2026 comes down to one question most comparisons skip: how cleanly does it run on your own box without Vercel? On that axis, Astro and React Router 7 (the merged Remix) self-host most cleanly, Next.js carries the heaviest hosting-feature footprint, and TanStack Start stays client-first while everyone else leans into React Server Components.

Why This Comparison Ignores the Vercel Default

Most “best React framework” posts assume one thing without saying it: a one-click Vercel deploy, edge functions on tap, and image optimization handled for you. Strip that away and the rankings shift. The framework that looks best on a managed platform is not always the one that runs cleanly on your own hardware.

For self-hosting real apps in 2026, pick Node.js 24 LTS for stable long-running processes, Bun 1.3 for install speed, and Deno 2.8 for single-binary deploys. On my own box, Bun installs an 847-package monorepo in 1.2 seconds versus npm’s 32, but Node still wins the 3am stability test.

Three runtimes now fight for the same job: running your server-side JavaScript. Node.js is the 16-year incumbent. Bun bets on raw speed. Deno bets on security and a single binary. This post compares them for one specific use: self-hosting a real app on hardware you own, not a synthetic hello-world race.

Hono is a ~14KB TypeScript web framework that runs on every modern JavaScript runtime with the same API. Write your routes once and ship to Bun , Deno , Cloudflare Workers , Node.js , AWS Lambda , Vercel Edge, Fastly Compute, or Netlify. No code changes needed. Hono builds on Web Standard APIs (Request, Response, fetch), which makes it small, fast, and far lighter than Express . It ships with middleware, validation, RPC, and streaming. The current stable release is v4.12.

You can build a fully working Markdown editor with synchronized live preview using a <textarea> for input, the marked library for parsing, and a debounced input event listener that re-renders on every keystroke. The whole thing fits in under 100 lines of vanilla JavaScript and CSS, with no build tools , no framework, and no npm install. One index.html file, one CDN script tag, double-click to open in a browser, and you are writing Markdown with a rendered preview next to your cursor.