Vue

Vue is an open-source JavaScript framework for building user interfaces. It renders a component tree in the browser, tracks state through a reactivity system that updates only what actually changed, and keeps templates close enough to plain HTML that a developer who knows markup can read one on their first day in the codebase.

What makes it useful to us is that adoption is incremental. Vue can be added to one page of an existing server-rendered application and take over a single widget, and that same component code runs unchanged inside a full build pipeline later. A team sitting on a large legacy application can modernise one screen at a time, shipping each step, instead of committing to a rewrite before anyone knows whether the approach holds.

The single-file component keeps a component's template, logic and scoped styles in one file. That sounds cosmetic and is not: changing a component is a change to one file, and the CSS that belongs to it cannot leak into a component someone else owns.

The official libraries are part of the framework rather than a community lottery. Routing, state management and the build toolchain are maintained by the same team as the core, versioned with it and documented in one place. The upgrade path is one decision instead of five, which is the thing that actually costs money over a decade.

What we get out of it on a typical build:

• Incremental adoption, so a legacy application can be modernised screen by screen with each step shipping on its own rather than waiting on a big-bang cutover.
• Server rendering and static generation through Nuxt where a page has to be indexed or paint fast, using the same components as the interactive parts.
• A reactivity model that removes a class of stale-render bugs, because what updates is derived from what changed rather than declared by hand.
• TypeScript throughout, so the contract between components is checked at build time instead of in QA.
• A genuinely deep hiring pool, and documentation good enough that it shortens the ramp for whoever inherits the codebase after us.

It is not our default for every front end, and we say which one we would pick before the decision is made rather than after. Where a client's own team is already fluent in React or Angular, that is nearly always the right constraint to keep: the framework a team can maintain beats the framework that scores better in isolation.

Vue's ecosystem is also smaller than React's at the edges. For mainstream needs that is invisible, but for a niche integration — a specific charting library, a vendor SDK shipped React-first — it can mean writing and maintaining a wrapper. That is a cost worth checking before committing, not after.