4 ms·
They are not people with more experience you are appealing to authority. The cold hard truth is that Angular got it so wrong the first go around that they had t
by kls 7y ago
They are not people with more experience you are appealing to authority. The cold hard truth is that Angular got it so wrong the first go around that they had to completely rewrite the framework. The very reason was that a lot of the early guys where just out of school and built a framework on theory. If you contrast this with React, guys in the trenched trying to build applications at scale for FB, they where built with totally different mindsets. The FB guys understood the render loops that has been a pattern in UI since the desktop days and has stuck around because it works. To this day two way data binding and template based logic are both a dumpster fire, that cause unmaintainable code and side effects that cause debugging to be more difficult.
This is just a bad idea:
https://angular.io/guide/template-syntax https://angular.io/guide/template-syntax
Without writing the tooling to debug it, to this day there is not said tooling.
- IggleSniggle 7y ago...well...on THIS day there is said tooling. In Angular 9.
- kls 7y agoThis is the most comprehensive document I can find on debugging in 9 and I still do not see a way to set a breakpoint in say a loop declared in a template. I may be missing something as I have not worked on an Angular project in probably 6 months. But I don't see template debugging I see being able to get reference to a component and then manipulate said component via dev tools. https://juristr.com/blog/2019/09/debugging-angular-ivy-console/ https://juristr.com/blog/2019/09/debugging-angular-ivy-conso...