4 ms·

I find Angular much more "boring" than react because it feels much closer to classical HTML/CSS/JS. React basically asks me to mix all of these, which can be d

I find Angular much more "boring" than react because it feels much closer to classical HTML/CSS/JS. React basically asks me to mix all of these, which can be distracting

westwing 6y ago
I arrived at the opposite opinion. React really only asks you to mix HTML (or representations of HTML) with JS, while Angular asks you to write some "not-quite-HTML-nor-JS" DSL. Angular is also impossible to use in a lean fashion. React doesn't require "create-react-app" or even JSX.
antihero 6y ago
I found Angular weirdly over-complicated for doing the same stuff React does.
- Alex3917 6y ago
  It was more complicated before version 1.5, now it’s basically the same. In the last year I think angular is likely the best framework again.
- dirtnugget 6y ago
  At first maybe but once projects become larger, its often preferable to have a complete toolset which is feature-complete and documented in the same place. I do not like spending time on things such as choosing which router to use, or which extension should be used to handle async operations in redux. Or wether we should write class-based or functional components. Or how to configure production builds. Or wether to use dispatchToProps or hooks. React has gotten quite messy over the years. In my last react project I encountered 3 out of those 5 questions in a 4 week span. Angular projects tend to have the same, reliable dependencies and structure. I admit that Angular adds some overhead if you have not worked with modules and observables, but it does give you a complete toolset to build very scalable frontends. And once you dive into ngrx and its ecosystem it becomes clear that Angular has quite some upsides, especially for enterprise software. There is a reason why NestJS adopted a lot of Angulars patterns such as modules and services. They make the code so much cleaner when used properly.
  - antihero 6y ago
    > I do not like spending time on things such as choosing which router to use, Build the app in such a way that you can change it. Or just use react-router. > wether we should write class-based or functional components Functional > Or wether to use dispatchToProps or hooks. Hooks. But I see what you mean, React's idiomatic patterns do change. Thing is, if you have a class based component you can still use it in amongst your functional hook-based ones. It's still compatible.
vyrotek 6y ago
Indeed. Modern Angular is a pleasure to work with. You get a lot of value and productivity right out of the box and it really shines for really large apps. The "boring" aspects help me focus on what I need to build and less how.
- dirtnugget 6y ago
  I really don’t understand all the hate, also occasionally here. Also I don’t understand why everyone is building with and hiring for react. Its main selling point is that it is "just a library, not a framework" which I also find to be its biggest disadvantage. When I build an application and I choose SPA, I want a framework, not a loose collection of libs. It’s a little like Django vs Flask. Sure Flask has less overhead but if I know what I am doing I can do 4 times as much with a framework like django in the same time, given that I know what it can do for me. Because I don’t spend time (more or less consciously) reinventing the wheel

I find Angular much more "boring" than react because it feels much closer to classical HTML/CSS/JS. React basically asks me to mix all of these, which can be distracting

westwing 6y ago

I arrived at the opposite opinion. React really only asks you to mix HTML (or representations of HTML) with JS, while Angular asks you to write some "not-quite-HTML-nor-JS" DSL. Angular is also impossible to use in a lean fashion. React doesn't require "create-react-app" or even JSX.

antihero 6y ago

I found Angular weirdly over-complicated for doing the same stuff React does.

Alex3917 6y ago
It was more complicated before version 1.5, now it’s basically the same. In the last year I think angular is likely the best framework again.
dirtnugget 6y ago
At first maybe but once projects become larger, its often preferable to have a complete toolset which is feature-complete and documented in the same place. I do not like spending time on things such as choosing which router to use, or which extension should be used to handle async operations in redux. Or wether we should write class-based or functional components. Or how to configure production builds. Or wether to use dispatchToProps or hooks. React has gotten quite messy over the years. In my last react project I encountered 3 out of those 5 questions in a 4 week span. Angular projects tend to have the same, reliable dependencies and structure. I admit that Angular adds some overhead if you have not worked with modules and observables, but it does give you a complete toolset to build very scalable frontends. And once you dive into ngrx and its ecosystem it becomes clear that Angular has quite some upsides, especially for enterprise software. There is a reason why NestJS adopted a lot of Angulars patterns such as modules and services. They make the code so much cleaner when used properly.
- antihero 6y ago
  > I do not like spending time on things such as choosing which router to use, Build the app in such a way that you can change it. Or just use react-router. > wether we should write class-based or functional components Functional > Or wether to use dispatchToProps or hooks. Hooks. But I see what you mean, React's idiomatic patterns do change. Thing is, if you have a class based component you can still use it in amongst your functional hook-based ones. It's still compatible.

vyrotek 6y ago

Indeed. Modern Angular is a pleasure to work with. You get a lot of value and productivity right out of the box and it really shines for really large apps. The "boring" aspects help me focus on what I need to build and less how.

dirtnugget 6y ago
I really don’t understand all the hate, also occasionally here. Also I don’t understand why everyone is building with and hiring for react. Its main selling point is that it is "just a library, not a framework" which I also find to be its biggest disadvantage. When I build an application and I choose SPA, I want a framework, not a loose collection of libs. It’s a little like Django vs Flask. Sure Flask has less overhead but if I know what I am doing I can do 4 times as much with a framework like django in the same time, given that I know what it can do for me. Because I don’t spend time (more or less consciously) reinventing the wheel