web dev//framework

A framework is a reusable body of software that supplies the structure of an application and calls the application's code at predefined extension points, so that routing, rendering, builds and conventions arrive as one coordinated set of defaults. That inversion of control distinguishes it from a library: you call a library; a framework often calls you.

A framework is a reusable body of software that supplies the structure of an application and calls the application's code at predefined extension points, so that routing, rendering, builds and conventions arrive as one coordinated set of defaults. That inversion of control distinguishes it from a library: you call a library; a framework often calls you.

React, Angular, Next.js, Astro, Express, and Hono solve different layers, so asking which framework is best usually leaves out the workload.

Framework value comes from coordinated defaults: routing, rendering, builds, deployment, conventions, and ecosystem. The same coordination creates migration cost and constrains unusual architectures.

The abstraction is cheapest when the product resembles the framework's expected application. Every deviation spends complexity budget fighting machinery originally intended to help.

A framework does not eliminate decisions. It makes a large batch of decisions together and asks whether you accept the bundle.