4 ms·
I agree with this. It's a mistake to characterise this solely as Angular vs. React though. It's really about these things, - Declarative UI as a pure function
by Wintamute 9y ago
I agree with this. It's a mistake to characterise this solely as Angular vs. React though. It's really about these things,
- Declarative UI as a pure function of state
- One way data flow
- Frameworks that use plain language features and functions, rather than template-like DSLs
No need for framework holy wars, but objective speaking these sorts of approaches are objectively the right future for UI development imo.
- jamra 9y agoAngular is mostly a declarative UI. I don't usually put logic in my templates. I do, however, like how react leans towards using language features instead of abstractions. Angular does one way data flow. It also allows for two way binding. The choice is the developer's. So your argument boils down to using language feature over the template DSL. I think it's more important to consider state management, code reuse, and inter component communication (perhaps also a part of state management if using something like Redux).