4 ms·

This feels like an argument made by somebody who has never built a serious project in either, and has instead formed an opinion based on quick glance at the res

This feels like an argument made by somebody who has never built a serious project in either, and has instead formed an opinion based on quick glance at the respective syntaxes. To me, Angular is what HTML and the DOM would look like if they had been designed from the beginning for application development: - Custom elements backed by controller classes. - Data-binding and event-binding syntax baked into HTML - Component style encapsulation, on by default. React seems far more like a project created by people who dislike front-end development: As I recall the genesis of the project was to replace traditional DOM mutation with a more PHP-esque approach of updating state and re-rendering everything, just as you would do on the back-end.

shadowmint 7y ago
Why does having a different opinion to you mean someone has no idea what they’re talking about, or has never used a thing “seriously“? I used to love angular, then I got a job which was a “| async” dumpster fire and spent a year watching a team of smart c# developers wallow in a mire of disaster so bad it became a two week regression to change a text field on a form. So full of amazing functional statement no one, even the original authors, could touch it without breaking something in the process. so. Your milage may vary. I no longer particularly like angular, personally, because I find it a chore to herd inexperienced FactoryInjectorConstructorFactoryPattern angular developers into not screwing things up. ...but talented team can do well with it too, and I’ve seen people screw up react projects too. It really is more about good practice and experience than framework, your personal preference is probably, like mine, basically irrelevant.
zdragnar 7y ago
I've shipped products using most major FE frameworks. Those things can be had by pretty much any of them. The biggest annoyance with angular is the excessive amount of baggage and boilerplate. Decorators aren't inheritable or composable. Because templates are strings, you need the hacky DI and superfluous module system to avoid tag name clashes. As for React, it is nothing like PHP. JSX is a macro for function calls that return objects; as such they are first-class data structures with all of the benefits you would expect. Yes, it is just a view layer and you need to bring more stuff in if you have a big project planned. If angular floats your boat that's great. The last time I used it was in a team of mostly C#, Java and Python enthusiasts. Once they figured out what was es2015, what was typescript, and what was Angual, the dev experience was generally reviled. (especially once they saw some react code). I generally don't say that I won't work with a technology, but after a year with it (and having years for AngularJS/1.x, React, Ember, Vue and Backbone under my toolbelt) I am content with saying that Angular sits with Backbone at the bottom of the pile of what I would choose to use again.
sdegutis 7y ago
Every time I look at Angular, I remember that they use string literals for both HTML and CSS which is strongly off-putting. Especially because for HTML, it becomes another template language like Vue.js, whereas React.js is just JavaScript with a simple and predictable syntax transformation.
- sixbrx 7y ago
  You see the template and css as literals in little Angular examples, but the normal case is that the literals are just names of the separate html and (s)css file names.
hesarenu 7y ago
React seems far more like a project created by people who dislike front-end development - that seems way off. For me react is the perfect fit for front-end development. You have syntax similar to html and logic in plain javascript. Angular is like some heavy java back end framework.
ng12 7y ago
> React seems far more like a project created by people who dislike front-end development This is a really poor characterization. I started using React because I love front-end and it was exactly what I wanted front-end development to be. It solved every one of the pain-points I was experiencing with a jQuery/Backbone/Handlebars stack.

shadowmint 7y ago

Why does having a different opinion to you mean someone has no idea what they’re talking about, or has never used a thing “seriously“? I used to love angular, then I got a job which was a “| async” dumpster fire and spent a year watching a team of smart c# developers wallow in a mire of disaster so bad it became a two week regression to change a text field on a form. So full of amazing functional statement no one, even the original authors, could touch it without breaking something in the process. so. Your milage may vary. I no longer particularly like angular, personally, because I find it a chore to herd inexperienced FactoryInjectorConstructorFactoryPattern angular developers into not screwing things up. ...but talented team can do well with it too, and I’ve seen people screw up react projects too. It really is more about good practice and experience than framework, your personal preference is probably, like mine, basically irrelevant.

zdragnar 7y ago

I've shipped products using most major FE frameworks. Those things can be had by pretty much any of them. The biggest annoyance with angular is the excessive amount of baggage and boilerplate. Decorators aren't inheritable or composable. Because templates are strings, you need the hacky DI and superfluous module system to avoid tag name clashes. As for React, it is nothing like PHP. JSX is a macro for function calls that return objects; as such they are first-class data structures with all of the benefits you would expect. Yes, it is just a view layer and you need to bring more stuff in if you have a big project planned. If angular floats your boat that's great. The last time I used it was in a team of mostly C#, Java and Python enthusiasts. Once they figured out what was es2015, what was typescript, and what was Angual, the dev experience was generally reviled. (especially once they saw some react code). I generally don't say that I won't work with a technology, but after a year with it (and having years for AngularJS/1.x, React, Ember, Vue and Backbone under my toolbelt) I am content with saying that Angular sits with Backbone at the bottom of the pile of what I would choose to use again.

sdegutis 7y ago

Every time I look at Angular, I remember that they use string literals for both HTML and CSS which is strongly off-putting. Especially because for HTML, it becomes another template language like Vue.js, whereas React.js is just JavaScript with a simple and predictable syntax transformation.

sixbrx 7y ago
You see the template and css as literals in little Angular examples, but the normal case is that the literals are just names of the separate html and (s)css file names.

hesarenu 7y ago

React seems far more like a project created by people who dislike front-end development - that seems way off. For me react is the perfect fit for front-end development. You have syntax similar to html and logic in plain javascript. Angular is like some heavy java back end framework.

ng12 7y ago

> React seems far more like a project created by people who dislike front-end development This is a really poor characterization. I started using React because I love front-end and it was exactly what I wanted front-end development to be. It solved every one of the pain-points I was experiencing with a jQuery/Backbone/Handlebars stack.