5 ms·

@alex3917 summarizes in comments below, and what are also similar reasons why I believe modern angular will “overtake” modern react/frameworks like next. Angul

by ramoz 4y ago

@alex3917 summarizes in comments below, and what are also similar reasons why I believe modern angular will “overtake” modern react/frameworks like next. Angular in 2022 is simpler than react. It’s what react was in 2015 when Angular 1.x was a complicated and annoying beast. Now, Angular is simple and pleasant; while my scaled, hooks infested, react apps make me feel like I’m handicapping myself.

hinkley 4y ago
It's very very difficult to get people to adopt systems that have already been labeled as failed. If Angular is indeed simple and pleasant, perhaps there's a space for a clone and a new name, like NodeJS versus Rails.
- ls15 4y ago
  Vue?
filoeleven 4y ago
> Angular in 2022 is simpler than react Surely you must be joking. You have to learn all of these things to make the tiniest CRUDdy app: - angular modules - angular template syntax - angular decorators - angular dependency injection - rxjs I mean, look at the FULL table of contents for their “Get data from a server” doc! [0] I can’t speak about next.js, it doesn’t fit my use case. But claiming that “Angular is simpler than React” is ludicrous. https://angular.io/tutorial/toh-pt6 https://angular.io/tutorial/toh-pt6
- blakblakarak 4y ago
  It's simpler once you know it. I bounce between Angular and React and whilst it's true that React is easier to get started, changes in the API (hooks, class vs functional componentns) and ecosystem (eg forms, UI Kits, state management, architecture etc) mean that I find it's a constant learning curve, whereas aside from a few minor changes Angular has been the same since V2.
- findingFounders 4y ago
  looks like Standalone Components, which are in preview in the latest v14, may yet see the deprecation of angular modules, or at least give more options to devs https://angular.io/guide/standalone-components https://angular.io/guide/standalone-components With decorators and dependency injection at least you're learning a concept which has been quite widely used across some popular languages/frameworks, there's a chance you'd already have come across these ideas in learning programming. rxjs definitely can take some learning time, though to get started with basic things like handle an api request with observable it doesn't take long. There's a whole lot you can do, and that power is quite useful for complex scenarios.
  - antonvs 4y ago
    For me Angular's use of rxjs is a killer feature. Our back end code relies heavily on streaming computations, and rxjs provides a great front end complement to that. Powerful tools often put people off because they appear complex. Often that complexity is at least partly an illusion - once you've learned the abstractions, much of what seemed to be complexity can actually be very simple.
    - findingFounders 4y ago
      yep i really like using rxjs now. i find using "await lastValueFrom(<observable>)" keeps code nicely readable and flat. it has 38m weekly downloads on npm so should be around for a good while.
  - filoeleven 4y ago
    I don’t want to use decorators. They’re another band-aid to keep OOP on life support. They are disguised functions applied to mutable objects in order to enhance their capabilities (or maybe to comply with type interfaces). Dependency injection is the exact same thing, only with different syntax.
damsta 4y ago
> Angular 1.x was a complicated and annoying beast For me Angular 1.x was simple and pleasant, first JS framework that I really liked to use back when MEAN stack was popular. Angular 2+ is what you call "complicated and annoying beast". > my scaled, hooks infested, react apps make me feel like I’m handicapping myself I know what you mean, I hope Vue 3+ or Solid will slowly replace React.
kobalsky 4y ago
> while my scaled, hooks infested, react apps make me feel like I’m handicapping myself nothing prevents you from just using classic classes with react. we have 0 hooks on our code and we are not missing out on any feature. I wish some of my other projects we are as easy to maintain and extend. react + flow + redux + sagas feel like a cheat code. it shouldn't be so easy to program javascript.

by ramoz 4y ago

hinkley 4y ago

It's very very difficult to get people to adopt systems that have already been labeled as failed. If Angular is indeed simple and pleasant, perhaps there's a space for a clone and a new name, like NodeJS versus Rails.

ls15 4y ago
Vue?

filoeleven 4y ago

> Angular in 2022 is simpler than react Surely you must be joking. You have to learn all of these things to make the tiniest CRUDdy app: - angular modules - angular template syntax - angular decorators - angular dependency injection - rxjs I mean, look at the FULL table of contents for their “Get data from a server” doc! [0] I can’t speak about next.js, it doesn’t fit my use case. But claiming that “Angular is simpler than React” is ludicrous. https://angular.io/tutorial/toh-pt6 https://angular.io/tutorial/toh-pt6

blakblakarak 4y ago
It's simpler once you know it. I bounce between Angular and React and whilst it's true that React is easier to get started, changes in the API (hooks, class vs functional componentns) and ecosystem (eg forms, UI Kits, state management, architecture etc) mean that I find it's a constant learning curve, whereas aside from a few minor changes Angular has been the same since V2.
findingFounders 4y ago
looks like Standalone Components, which are in preview in the latest v14, may yet see the deprecation of angular modules, or at least give more options to devs https://angular.io/guide/standalone-components https://angular.io/guide/standalone-components With decorators and dependency injection at least you're learning a concept which has been quite widely used across some popular languages/frameworks, there's a chance you'd already have come across these ideas in learning programming. rxjs definitely can take some learning time, though to get started with basic things like handle an api request with observable it doesn't take long. There's a whole lot you can do, and that power is quite useful for complex scenarios.
- antonvs 4y ago
  For me Angular's use of rxjs is a killer feature. Our back end code relies heavily on streaming computations, and rxjs provides a great front end complement to that. Powerful tools often put people off because they appear complex. Often that complexity is at least partly an illusion - once you've learned the abstractions, much of what seemed to be complexity can actually be very simple.
  - findingFounders 4y ago
    yep i really like using rxjs now. i find using "await lastValueFrom(<observable>)" keeps code nicely readable and flat. it has 38m weekly downloads on npm so should be around for a good while.
- filoeleven 4y ago
  I don’t want to use decorators. They’re another band-aid to keep OOP on life support. They are disguised functions applied to mutable objects in order to enhance their capabilities (or maybe to comply with type interfaces). Dependency injection is the exact same thing, only with different syntax.

damsta 4y ago

> Angular 1.x was a complicated and annoying beast For me Angular 1.x was simple and pleasant, first JS framework that I really liked to use back when MEAN stack was popular. Angular 2+ is what you call "complicated and annoying beast". > my scaled, hooks infested, react apps make me feel like I’m handicapping myself I know what you mean, I hope Vue 3+ or Solid will slowly replace React.

kobalsky 4y ago

> while my scaled, hooks infested, react apps make me feel like I’m handicapping myself nothing prevents you from just using classic classes with react. we have 0 hooks on our code and we are not missing out on any feature. I wish some of my other projects we are as easy to maintain and extend. react + flow + redux + sagas feel like a cheat code. it shouldn't be so easy to program javascript.