AI summary by TwinMind

JavaScript Framework Tier List

Theo - t3․gg

40m 57s

Framework Ranking Overview

  • Ranking every JavaScript framework in tier list format (S, A, B, C, D, F)
  • Using vanilla JavaScript as C-tier baseline reference point
  • Evaluating frameworks based on developer experience, syntax, community, and impact

Individual Framework Rankings

S-Tier Frameworks

  • jQuery: S-tier
    • Foundation of modern internet
    • Still present on majority of websites
    • Fantastic developer experience
    • Script tag setup approach
  • Solid: S-tier (just behind jQuery)
    • Best performance benchmarks, nearly vanilla JS speed
    • Uses JSX but compiles to signals-based reactivity
    • Create signal, create effect primitives
    • HTM support for no-build-step development
    • Solid Start making significant progress
    • Two S's in name = bonus points

A-Tier Frameworks

  • Angular: A-tier
    • Massive historical impact on web development
    • Enabled large codebases with hundreds of developers
    • Kickstarted component-based web architecture
    • Transition from AngularJS to Angular was significant
    • Personal hatred for development experience but acknowledges importance
  • Lit: A-tier (moved up from B)
    • Built around web components standards
    • Creates actual HTML elements usable in browser
    • Good for reusable components across projects
    • Vanilla JavaScript compatibility
    • Pleasant abstraction over raw web components
  • Nuxt: A-tier (highest-rated meta framework)
    • Full-stack plugin system
    • TypeScript-based RPC solution with automatic type inference
    • Use fetch with network call deduplication
    • Dollar sign fetch with type safety
    • Only way presenter would use Vue
    • Compelling meta framework evolution

B-Tier Frameworks

  • Handlebars: B-tier (slightly above vanilla JS)
    • Important templating language concept
    • Standardized HTML generation from JavaScript
    • Opposite approach to jQuery (generate vs manipulate)
    • Historical significance in JS/HTML relationship
  • Preact: B-tier
    • Fast React alternative focused on bundle size
    • Strict bundle size rules (add feature = delete equivalent code)
    • HTM support for no-transpilation JSX
    • Class components and hooks support
    • First to implement signals in React-like framework
    • Educational value for understanding React internals
    • Recent performance benchmarks not as competitive
  • Next.js: B-tier
    • S-tier for extensibility and abuse potential
    • Core primitives historically painful (getServerSideProps)
    • API directory excellent for JSON endpoints
    • Great with tRPC integration
    • App router improvements but still issues with file-based routing
    • Server components value comes from React, not Next
  • Svelte: B-tier (front of B-tier)
    • Historically important, challenged React dominance
    • Rethinking Reactivity talk was influential
    • Single file component architecture commitment
    • Custom templating syntax reinvents JavaScript in HTML
    • #each syntax: #each array.from(Array(6).keys()) as row
    • @debug alternative to console.log
    • Syntax preferences over React's JSX approach

C-Tier Frameworks

  • Vanilla JavaScript: C-tier (baseline)
    • Solid middle ground reference point
    • Won't make things worse or better
    • All other frameworks compared against this baseline
  • Quick: C-tier (slightly better than vanilla JS)
    • Created by Misko (original Angular creator)
    • Focuses on resumability vs hydration
    • Addresses JavaScript bundle size, time-to-interactive issues
    • Component$() syntax for component definition
    • Hybrid of Solid and Remix concepts
    • Resumability benefits questionable for most use cases
    • Other frameworks catching up with hybrid hydration

D-Tier Frameworks

  • Alpine.js: D-tier
    • Lightweight framework with script tag setup
    • 15 attributes, 6 properties, 2 methods
    • Vue-syntax for mid-version of HTMX
    • JavaScript-in-string approach
    • Would have ranked higher before HTMX relevance
  • Vue: Low A-tier (but mentioned for comparison)
    • Incredible international community
    • Docs internationalized rapidly
    • Single file component trend starter
    • v-for syntax with specific runtime requirements
    • Vue JSX exists but <33% adoption rate
    • Less dynamic than pure JavaScript approaches
    • Vue Vapor (Solid-like rewrite) anticipated

F-Tier Frameworks

  • Astro: F-tier
    • Not actually a JavaScript framework
    • Ships no browser-running code
    • HTML generation on server only
    • Can mount React components but no native router/JS
    • Imposter framework
  • Ember: F-tier
    • Caused presenter to initially dislike web development
    • Heavy code generation approach
    • Handlebars-based templating (HBS)
    • @tracked decorator syntax
    • Template/JavaScript separation with non-deterministic behavior
    • Development mode required to catch binding errors
    • GitHub highlighting doesn't work properly
  • Remix: F-tier (same tier as Quick)
    • Important for web evolution but wouldn't use personally
    • Route-level loader/action separation problematic
    • Non-deterministic component/data relationships
    • Moving components breaks functionality silently
    • Switch statements required for multiple actions per route
    • Normalized important patterns (streaming, TTFB, server React)
    • Influenced Next.js and React development
  • Gatsby: F-tier
    • React framework with HTML page generation
    • Massive GraphQL layer for data management
    • Plugin system for WordPress, Markdown integration
    • Extremely painful development experience
    • Acquired by Netlify, framework largely abandoned
    • Worst possible approach to React website generation
  • Flutter Web: F-tier
    • Escapes web primitives entirely
    • Canvas-based rendering
    • No DOM, no button elements
    • Accessibility issues (screen readers)
    • Even Flutter advocates don't recommend web usage
  • Elm: D-tier
    • Functional programming language, not just framework
    • Benchmarks against outdated frameworks (Angular 1/2, old React)
    • Nested vertical syntax approach
    • Manual text/element assignment with arrays
    • Too far into FP territory for practical adoption
    • Minimal recent development/adoption

Special Mentions

  • HTMX: F-tier (not JavaScript framework)
    • Allows backend developers to create interactive web apps
    • Eliminates need for JavaScript frameworks
    • HX-post, HX-swap-outer-html attributes
    • Works with any backend language
    • Solves different problem than JavaScript frameworks
  • Flash: S-tier (joke ranking)
    • All best games made in Flash
    • Android support existed briefly
    • Touchscreen friendly
    • Historical significance

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome