Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 9.0

blog.angular.io

Post reply on HN
Print view View original

61–70 of 308 posts

Re: Angular 9.0

#61

Post by joshschreuder »

tony wrote: post #46

One of the nice things that Angular has you don't see in the post is... very polite and courteous maintainers! https://github.com/angular/angular/pull/33717#issuecomment-5... This was a fast release cycle. It was back in November 2019 we were talking about 3.7, and now it's in. I'm not even thinking about Ivy. But it's nice to have all the nice comforts of typescript ready and working out of the box. (I mainly work i…

Igor seems like a good dude. I used to follow his talks and stuff from back in the AngularJS days.

Re: Angular 9.0

#63

Post by randall »

_xnmw wrote: post #28
topspin wrote: 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.

React was a mistake of the last decade. React itself is a great academic idea (i.e. pure functions, composability), but the whole React-Redux boilerplate mess (I dare not call it an "ecosystem" because that word implies harmony of some sort) is the the result of an entire generation of code monkeys and job seekers who didn't design their technology stack with any real engineering consideration, but rather on the basi…

Not to interrupt a good rant against tech (in this era... very brave, btw) but you should look at react with the context api. I think everyone who’s used it is glad it removed redux’s boilerplate insanity. There’s even some other frameworks (the name escapes me now) that are like boilerplateless redux if ppl like that style of event driven state updates.

Re: Angular 9.0

#64

Post by no_wizard »

Anyone know what the real world sizes of the bundles are now? Last I used Angular I couldn’t get a bundle smaller than like 250-300kb

Re: Angular 9.0

#65

Post by vips7L »

treeman79 wrote: post #10
vips7L wrote: 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 company is in the process of jQuery to React transition. It feels like it's taking a little longer as well.

Re: Angular 9.0

#66

Post by dfsegoat »

Is there still a clear path from angularjs 1.x onto angular 9.0? Anyone done it recently?

Supporting a large 1.x codebase right now, and would love to start incrementally moving to angular.

Re: Angular 9.0

#67

Post by pier25 »

ng12 wrote: post #54
topspin wrote: 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.

Bundle size and start time are much more important metrics IMO unless you have a high perf use case. Like you said, most of these are fast enough for the majority of uses cases.

Re: Angular 9.0

#68

Post by acemarke »

randall wrote: post #63
_xnmw wrote: post #28

Earlier quoted context omitted.

React was a mistake of the last decade. React itself is a great academic idea (i.e. pure functions, composability), but the whole React-Redux boilerplate mess (I dare not call it an "ecosystem" because that word implies harmony of some sort) is the the result of an entire generation of code monkeys and job seekers who didn't design their technology stack with any real engineering consideration, but rather on the basi…

Not to interrupt a good rant against tech (in this era... very brave, btw) but you should look at react with the context api. I think everyone who’s used it is glad it removed redux’s boilerplate insanity. There’s even some other frameworks (the name escapes me now) that are like boilerplateless redux if ppl like that style of event driven state updates.

Hi, I'm a Redux maintainer.

Please check out our new official Redux Toolkit package. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once:

https://redux-toolkit.js.org

Also, note that we have a new "Style Guide" docs page which specifically recommends patterns that we feel will lead to simpler code, like the "ducks" structure for single-file Redux logic:

https://redux.js.org/style-guide/style-guide

Finally, we're currently working on a major rewrite of the Redux core docs, with the goals of updating them for today's target audience and teaching easier-to-use patterns:

https://github.com/reduxjs/redux/issues/3592

(and by "we" I basically mean "me", since I'm not getting a lot of help with this effort so far.)

I'll also point out that while Context is a great tool for making data available to a nested subtree of components, it has major limitations in terms of processing frequent updates. We tried to use it internally in React-Redux v6, and it just wasn't sufficiently fast enough, which is why we had to rewrite the internals again in v7 to use direct subscriptions instead. So, very useful, but not a replacement for Redux.

Re: Angular 9.0

#69

Post by EugeneOZ »

ng12 wrote: post #31
pacala wrote: post #12

Earlier quoted context omitted.

Angular: Learn about property binding, event binding, pipes, templates, views, metadata, attribute directives, structural directives, services, modules, components, injectors. React: Write a function that generates a piece of HTML. Use standard event handlers to manage user interactions. Update state via setState methods. Ship it.

The first time I saw this in Angular's material implementation I was completely floored: https://material.angular.io/components/dialog/overview#shari... The method for passing data to a dialog component is to import a magic constant and inject a data field into it's constructor? It's a completely over-engineered, nonsensical solution for a problem that doesn't even exist in React. There's so much stuff you have to be…

Don't use this library as an example of Angular code. I've written dozens of Angular apps and none of them were so over-engineered. AngularMaterial is a good example how to not design API. I'm sorry if it insults some people - we all make mistakes, it's ok, I'm sure you'll next library will be better and I understand it's too late to change API in a project, when some huge Google apps are using it.

Re: Angular 9.0

#70

Post by Jasper_ »

ng12 wrote: post #54
topspin wrote: 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.

Then why are all the React-based web apps I use so slow?
Post reply on HN