Web Frameworks & Technologies 🌐

A JavaScript runtime built on Chrome's V8 engine that lets JS run outside the browser — the single most-used web technology, powering the entire modern JS backend ecosystem.

A secure-by-default JavaScript/TypeScript runtime from Node.js's original creator — built-in TypeScript support and permissions sandboxing, positioned as Node's modern successor.

Meta's component-based UI library — the single most-used frontend tool for building interactive interfaces, with a component model most other frameworks have converged toward.

The DOM manipulation library that dominated web development in the 2010s — largely superseded by modern frameworks for new projects, but still running on a massive share of existing websites.

Google's full-featured frontend framework — an opinionated, batteries-included framework (routing, forms, HTTP client all built in) favored in large enterprise applications.

A progressive frontend framework designed to be adopted incrementally — simpler learning curve than React or Angular, popular for both small widgets and full single-page apps.

The original Angular (version 1.x) — a completely different codebase from modern Angular 2+, now in legacy maintenance mode but still running many older enterprise apps.

A frontend framework that shifts work to compile time — instead of shipping a runtime framework to the browser, Svelte compiles your components into tiny, highly optimized vanilla JS.

The most popular React meta-framework — adds server-side rendering, file-based routing, and API routes on top of React, and is the default way most new React apps get built.

Vue's answer to Next.js — a full-stack meta-framework adding server-side rendering, file-based routing, and auto-imports on top of Vue.

A content-first meta-framework built around shipping zero JavaScript by default — renders static HTML and only hydrates interactive "islands," ideal for content sites and blogs.

The minimal, unopinionated web framework for Node.js — the most common way to build an HTTP API in Node, and the foundation many other Node frameworks build on top of.

A structured, TypeScript-first Node.js framework inspired by Angular's architecture — built-in dependency injection and module system for large, maintainable backend codebases.

A Node.js web framework built specifically for speed — a plugin architecture and schema-based validation, aimed at teams that have outgrown Express's raw performance.

A modern Python API framework built for speed and automatic docs — generates interactive OpenAPI documentation from your code's type hints, and is the fastest-rising Python web framework.

A minimal, unopinionated Python web framework — gives you routing and request handling with almost nothing decided for you, popular for small APIs and projects that want full control.

Python's "batteries-included" web framework — an ORM, admin panel, auth system, and templating engine all built in, the standard choice for building a full web app quickly in Python.

The standard framework for building production Java applications — auto-configuration and an embedded server remove most of the boilerplate that made older Spring apps painful to set up.

Microsoft's modern, cross-platform web framework for .NET — the rewritten, open-source successor to classic ASP.NET, running on Windows, Mac, and Linux.

The original, Windows-only .NET web framework that predates ASP.NET Core — still running a large amount of legacy enterprise .NET software built before the cross-platform rewrite.

Microsoft's framework for building interactive web UIs in C# instead of JavaScript — runs either in the browser via WebAssembly or on the server, for teams that want to stay in .NET end to end.

The content management system behind a huge share of the entire web — a plugin/theme ecosystem lets non-developers build full sites, while developers extend it with custom PHP.

The most popular modern PHP framework — an elegant, batteries-included framework (ORM, auth, queues, templating) that made PHP development feel modern again.

A mature PHP framework and set of reusable components — many of Symfony's components are used inside Laravel and other PHP projects, making it foundational to the PHP ecosystem.

An older, highly flexible open-source CMS — favored for large, complex sites (government, universities, media) that need fine-grained content modeling beyond what WordPress offers.

The original "convention over configuration" full-stack framework — its productivity-first philosophy influenced the design of nearly every batteries-included framework that came after it.

A Rust web framework built by the Tokio async-runtime team — type-safe routing and extremely high performance, popular for Rust developers building high-throughput APIs.

A web framework for Elixir built on the Erlang VM — famous for handling enormous numbers of concurrent real-time connections (chat, live dashboards) with very low resource use.