3 ms·
You separate your presentation from your business logic in React. What React gives you that Angular doesn't is the ability to separate your presentational logic
by woah 10y ago
You separate your presentation from your business logic in React. What React gives you that Angular doesn't is the ability to separate your presentational logic from your business logic. Angular makes you put presentational logic in with your business logic because presentational logic simply cannot be expressed with the templating format.
I would argue that a distinction that you make yourself, based on your application's architecture is more meaningful and useful than one made by some arbitrary separation of source file formats.
- RodericDay 10y agoAll the React stuff is starting to sound a bit to me like "MongoDB is web-scale"
- dev360 10y agoNot really. I think a key distinction is summed up in this quote: "Angular 2 continues to put “JS” into HTML. React puts “HTML” into JS." See: https://medium.freecodecamp.com/angular-2-versus-react-there-will-be-blood-66595faafd51#.1kuf8qlpd https://medium.freecodecamp.com/angular-2-versus-react-there... This influences to some extent what you can do with the frameworks and how your code is organized. I like the fact that since my rendering is essentially JS in React, then I can structure my code better with OO to solve problems (inheritance where appropriate, helper classes, patterns etc). In Angular, its just a awful mess of ng-* statements for flow of control. All you can really do to tame it is to use composition or to mix-in behavior via directives.