loading...

re: Angular struggles in 2020 VIEW POST

TOP OF THREAD FULL DISCUSSION
re: So lets make 2 thought experiments: We continue (the Angular team, and community) down this same path for the foreseeable future. What happens? W...
 

I would propose two things: First, change the governance model of the Angular project to be more transparent and more open to collaboration with the community, particularly non-Google entities like Nrwl. This could involve transferring ownership of the project from Google to a foundation.

Second, be realistic about engineering capacity vs. ambition and reduce the scope of the framework's core to what can actually be maintained. Move some parts of the framework out of the core into community-managed projects. For example, both reactive forms and the router have seen very little attention from the core team, but as long as they are official parts of the framework, it is very difficult for alternative implementations to gain traction.

 
 

Thank you, those are great suggestions. I don't have an answer, but something needs to change. We need to be discussing issues and alternatives like these in the open.

 

Move some parts of the framework out of the core into community-managed projects.

Hell no, look where did that get react native

Code of Conduct Report abuse