Live data from Hacker News

Angular 9.0

blog.angular.io

51–60 of 308 posts

Re: Angular 9.0

#51

Earlier quoted context omitted.

because React's stance is that it's a rare enough case in their experience, so they don't spend time optimizing for it. that metric is slower in general because libs with simple reconciliation strategies will tend to do work for every row between the two swapped ones (2,998).

So what's the benefit of more complex ones like react's?

Popularity.

The ecosystem is bigger and there are more devs available.

Re: Angular 9.0

#52
post #14

Earlier quoted context omitted.

What happened to React? It's on the wrong end of almost all of those micro benchmarks. I know micro benchmarks don't tell the whole story, but when you consistently wind up on the slow end it's not a good look.

> What happened to React? react has always been approx where it is now. but there are a lot more faster libs in the table.

> react has always been approx where it is now

Didn't know that. What I thought I knew is based on years of breathless claims about React's great performance. This is eye opening. Even Angular 8 does better in these benchmarks.

Re: Angular 9.0

#53

Earlier quoted context omitted.

because React's stance is that it's a rare enough case in their experience, so they don't spend time optimizing for it. that metric is slower in general because libs with simple reconciliation strategies will tend to do work for every row between the two swapped ones (2,998).

So what's the benefit of more complex ones like react's?

By choosing React I'm optimizing for my time. I'll always add a framework that adds a tiny performance overhead if it means I can develop and maintain features easier.

That said -- performance characteristics like this are rarely interesting to me. The vast majority of "performance issues" I've encountered have to do with high-level architecture and/or network issues. I've never given up on a framework because it couldn't swap two DOM nodes fast enough.

Re: Angular 9.0

#54
post #52

Earlier quoted context omitted.

> What happened to React? react has always been approx where it is now. but there are a lot more faster libs in the table.

> react has always been approx where it is now Didn't know that. What I thought I knew is based on years of breathless claims about React's great performance. This is eye opening. Even Angular 8 does better in these benchmarks.

I think the breathless claims of performance are because for what React is doing -- storing the entire application tree using virtual DOM and seamlessly rendering updates -- it is really impressive. The fact that it is has similar performance as some much more naive frameworks is pretty amazing. In practice all of these frameworks are fast enough that you wouldn't notice unless you were doing something really crazy.

Re: Angular 9.0

#55

Why is Angular so less popular than React?

I am working on creating a web app now and for some reason decided to learn Dart and AngularDart at the same and do it with these technologies and it's close to being nightmarish. There are way too many concepts and things that tie together sort-of magically -- all to get a few form fields on a screen. I wonder how people come back to fix issues or add features in their Angular app after a few months away from it.

That said, I think, for bigger groups/companies working on a complex product, I can see that Angular ensures a certain level of "architecture" and code organized correctly instead of being coded to each dev's personal style.

But way too complex for single-person apps or for simple SPAs.

All that to say Angular is less popular because it is too complex to learn and use quickly.

Re: Angular 9.0

#56
post #7

Earlier quoted context omitted.

Probably because its a larger learning curve and its a lot more "framework".

Saw a 2 man team that got features done in a couple of weeks on jquery move to angular and turn into a 15 man team that took months on each feature. Management was very happy with how modern the stack felt Sales came to a halt for 2 years since features came to a halt. Turns out Angular is freaky hard to do right.

My old company did the jquery to angular conversion when angular was still alpha. Initial curve was steep because no one was used to doing things that way. After that we were just as quick if not a little quicker. I did a pretty big angular 2 e-commerce site from scratch by myself in 6 months shortly after angular 2 came out. Just use the framework how it's supposed to be used and it all works fine.

Re: Angular 9.0

#57
post #32

Earlier quoted context omitted.

You don't need to understand hooks to use react.

You have a looser definition of "to use" than me. Let's agree to disagree.

If your definition of usage excludes the hordes of feature-rich production React codebases with no hooks (hooks being a relatively recent React addition), I'd call that definition...counter intuitive.

Re: Angular 9.0

#58
post #54
post #52

Earlier quoted context omitted.

> react has always been approx where it is now Didn't know that. What I thought I knew is based on years of breathless claims about React's great performance. This is eye opening. Even Angular 8 does better in these benchmarks.

I think the breathless claims of performance are because for what React is doing -- storing the entire application tree using virtual DOM and seamlessly rendering updates -- it is really impressive. The fact that it is has similar performance as some much more naive frameworks is pretty amazing. In practice all of these frameworks are fast enough that you wouldn't notice unless you were doing something really crazy.

Yes, it's an admirable design. I've used it. I know. And no, nothing I've done with it has been intolerably slow. Although now I'm starting to wonder about some responsiveness issues I've experienced...

I also wonder if batteries care about elegance. Not really they don't. If one makes the highly likely assumption that these micro benchmarks are a measure of efficiency then it's actually difficult to do worse than React regarding battery life, heat, etc.

Very interesting.

Re: Angular 9.0

#59

Why is Angular so less popular than React?

Opinionated (professionally engineered structure) vs. Simple template system.

There’s no good or bad. As in any architectural adoption, it should’ve based on your team’s capabilities and support capabilities.

Experience matters too. There are good reasons to use either platform.

Re: Angular 9.0

#60

Why is Angular so less popular than React?

For me, I was first getting into web development before Angular 2 was out. I thought it was super cool that I could make an incrementing counter and a to do list but just couldn't figure it all out. I then tried React and it just kind of made sense. Since then from the sidelines I've heard Angular has gotten much better but personally don't see any reason to use anything other than React at this point in time.

I’m also starting to feel like if anything will dethrone React, it’ll probably be Vue or Svelte.
Post reply on HN