Angular VS Polymer

source: https://github.com/angular/angular/issues/46542

Besides the dangers, mentioned by Angular docs (infinite loops, change detection errors), there is another thing, that might be quite nasty: effects are executed in a reactive context, and any code you call in effect, will be executed in a reactive context. If that code reads some signals, they will be added as dependencies to your effect. Here Alex Rickabaugh explains the details.

In June 2023, the Angular team raised a new RFC to implement control flow syntaxes within Angular. They gave the following rationale for introducing control flow syntax:

For scheduling, I use awesome code I found in the Angular source code.

Just to give you more context, I led the migration of several AngularJS applications to the newer Angular Framework. My client finally decided to make that move following the AngularJS deprecation announcement (stay up to date please 🙏)️.

Link — angular/CONTRIBUTING.md

Angular v17 was released some months ago with a ton of new features, a brand new logo and the new blog angular.dev.

The Angular renaissance is still ongoing. MiniRx is part of that renaissance and released a new Signal-based state management library for Angular: MiniRx Signal Store.

Oh, and I know that Wappalyzer detects that Youtube uses Polymer, but here's the thing if you go to the Polymer docs it clearly says "The Polymer library is in maintenance mode. For new development, we recommend Lit."

Polymer - DEAD Recently

It is an open-source JavaScript library based upon Web Components. It is developed by Google. Polymer helps us to create custom elements for building web applications. It's much easier and faster to create custom elements that work like DOM elements.

At least for the YouTube example, if memory serves, they often use Polymer web components for page templating and layout. When you style components through these, oftentimes the CSS styling ends up inline on the page the components are included in.