Angular code wouldn't use any of these techniques:
- the use of Proxy()
- calling compile(),
- using a querySelector to bind elements
- Manually wiring up click handlers
But, I'm not sure that's what the author is trying to do -- I think they're trying to show what is going on under the hood, coded in pure JS.In that context, it's probably relevant to show this (assuming it's indicative of what Angular actually does -- of that I'm less sure)
My framework of choice is Angular and the example is somewhat accurate, even if it shows just a small slice of the system.
Indeed Angular components start off with a compilation step (which doesn't have to be done entirely at runtime) and there's a system in place to react to data changes and events in the template - can't confirm whether it's using Proxies though.
But there's also a whole change detection system which reacts to event listeners firing, HTTP requests, timeouts etc. and decides which components to update and how.
Nowadays there are also signals, which add another layer on top of all that.
Overall Angular's internals are a massively complicated beast and few people have a good grasp of them (I've met some - would not recommend doing what they were doing). Net effect is that its development as a framework is slow. Personally I see it as a feature.