It's also apparent that these issues can be addressed in classes, but doing so would disrupt the current mental model, potentially eliminating ngOnChanges, ngOnInit, etc. I see the benefits of a functional approach, but maybe a rebranding—like "AngularFN"—would be more fitting & helps with resources

Through all this, one thing is clear: simplifying authoring means altering how the view works, which could lead to major breaking changes. The timing around inputs and outputs needs adjusting, and some lifecycle methods (though Destroy is still necessary) are superfluous.

I think a functional approach would benefit from its own injector, allowing it to manage a factory returning itself—minimal changes would be needed. Yet, a "factory" is still required, so I'm exploring this within the view layer.

That said, I still have a lot to refine in the Component Factory and the view itself. It seems a new factory could resolve many issues without a major rewrite. However, creating subcomponents and determining the best place to handle these remains challenging.

I've modified the Component Factory and the view structure (still refining this) but it does render. One clear benefit is improved debugging. Instead of managing CTX and its values passed into the template, everything is directly accessible, including the values!

We don't need a massive ecological change that's detrimental to businesses and the ecosystem. The TreatyJS fork of Angular improved authoring with only minor adjustments, While improves can be made we don't need a reset or AngularFN

Find out more here:
lostdeveloper.medium.com/angular-auth...

#Angular is at a cross road, many of the "show case" been focus on using directives or creating components. But what about creation of decorators and structural directives. Are these going to be just normal JS function calls?

This is breaking Angular. Remain same or RE-BRAND

Many clients i've dealt with said their chose angular because of its stability and flexibility. However, alot are considering new projects in React because of its eco system.

Anything other than the 3rd (which should still ideally be in the decorators) will push more to react!

We should stop looking at GDS and inner circles for whats best for angular.

You are about to recommend breaking changes to everything and force a huge retrain and resources. Enterprise will not like this. Every day devs will not like this. React and vue (more react) has a far premiere eco system