4 ms·
I think Angular really delivered after they finally worked out how to do emit optimized code (eg. the Ivy rendering engine). What is (was?) problematic with An
by pas 5y ago
I think Angular really delivered after they finally worked out how to do emit optimized code (eg. the Ivy rendering engine).
What is (was?) problematic with Angular is the toxic leadership: https://medium.com/@jeffbcross/jeffs-letter-to-the-angular-team-and-community-5367934a16c9 https://medium.com/@jeffbcross/jeffs-letter-to-the-angular-t...
But there are great things happening. The wider community has solutions for everything. (For example here's the "reactive forms are not strongly typed" issue [0] that showcases both the good and the bad. The need for this feature has clearly emerged in 2016. People stepped up and a PR was created, but ... basically no signal from the Angular team. Of course using a wrapper was an easy workaround with a distinctly sour taste in the mouth. Then finally something happened and an Angular team member now seems to be working on it in "full steam ahead" mode.)
I recently had to maintain a large React + NestJS application and I was seriously considering organizing a terrorist cell to go back in time and ...
[0] https://github.com/angular/angular/issues/13721 https://github.com/angular/angular/issues/13721