Google: Angular and Wiz Are Merging

Google is merging its public Angular framework with Wiz, an internal web framework used for products like Search and YouTube, aiming to share performance features such as fine-grained code loading and signals-based reactivity. Developers are split: some welcome recent Angular improvements and hope dogfooding will strengthen the framework, while others are frustrated by Angular’s complexity, RxJS-heavy patterns, and Google’s broader track record of confusing product strategy and stagnation. Questions remain about real-world performance gains, migration pain for large codebases, and whether this convergence will meaningfully change Google’s often-criticized web UX.

What Wiz Is and How It’s Used

  • Wiz is an internal Google web framework powering latency‑sensitive consumer apps (e.g., Search, YouTube, Meet, Photos), historically Java + Soy templates + JS with a jQuery‑like API.
  • It’s tightly coupled to Google’s tech stack and has prioritized performance over ergonomics; some insiders describe it as outdated, slow to build, and unpleasant to work with.
  • Others challenge the “performance first” claim, citing heavy, sluggish sites like YouTube as counter‑evidence.

Nature of the Angular–Wiz “Merge”

  • Currently more of a convergence and code sharing than a single unified framework.
  • Angular Signals are already used in Wiz (e.g., YouTube mobile web).
  • Wiz is bringing ideas like very fine‑grained, interaction‑driven code loading and “resumability” concepts into Angular.
  • Long‑term goal stated as “merging,” but it may remain two coexisting frameworks; details to come in a blog post.
  • Parts of Wiz will effectively become open source “via Angular.”

Impact on Angular and Developer Experience

  • Angular is widely used internally at Google for tools and some public products (e.g., GCP console, Gemini web).
  • Planned/ongoing improvements: signals, partial hydration, deferred views, finer code splitting, reduced boilerplate.
  • RxJS is being made optional; core now has minimal dependency, with interop packages for those who want it.
  • Migration to new template syntax and signals is reported as tooling‑assisted and relatively painless by some, but others fear another AngularJS→Angular‑style disruption.

Community Sentiment on Angular

  • Strong split:
    • Critics: Angular is verbose, complex, RxJS/ngrx‑heavy, hard to reason about, and painful at scale; Angular Material “legacy” has blocked upgrades for some.
    • Supporters: Prefer Angular’s structure, DI, and “batteries‑included” approach for large enterprise apps; see recent versions as a major improvement.
  • Comparisons: Some prefer Vue or Svelte for simplicity; React is seen by some as equally problematic but in different ways (JSX, npm ecosystem).

Trust in Google and Broader Context

  • Many express skepticism toward new Google initiatives due to past cancellations, internal politics, and perceived decline in product quality.
  • Others note that, despite cultural/strategy concerns, Google’s financials and cloud revenue remain strong, so the company isn’t “failing,” even if underperforming its potential.