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

91–100 of 308 posts

Re: Angular 9.0

#91

Post by zaphirplane »

kabes wrote: post #77
qwerty456127 wrote: post #6

Why is Angular so less popular than React?

I've used both for non-trivial apps. I find angular heavily over-engineered. The problem is not just the learning curve, but the fact it becomes almost impossible to do anything the framework authors didn't envisage. React is just plain functions so you can do whatever you want, it never got in my way. Now, if angular would prove substantially better in terms of performance or maintainability or so, that might've bee…

That is an unfair comparison a fairer one is react + redux + hooks + middleware thunk + routing vs angular. You are still probably right in what is simpler. Just angular is kind of the kitchen sink option

Re: Angular 9.0

#93

Post by _the_inflator »

pacala wrote: post #12
qwerty456127 wrote: post #6

Why is Angular so less popular than React?

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.

Angular really shines in Enterprise context. 13+ teams and all use the same stack. Enter React and you are in maintenance hell, is my experience.

Re: Angular 9.0

#94

Post by monadic2 »

Pmop wrote: post #86
_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…

Oh man, don't say it. I've just started to learn React to improve my chances of landing into my first job, since all Java positions are either full-time or requires >4 years of previous relevant experience.

For better or worse, react is and will remain very employable.

Re: Angular 9.0

#95

Post by chrisco255 »

Jasper_ wrote: post #70
ng12 wrote: post #54

Earlier quoted context omitted.

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?

Facebook and Twitter are slow?

Re: Angular 9.0

#96

Post by manigandham »

Jasper_ wrote: post #70
ng12 wrote: post #54

Earlier quoted context omitted.

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?

Poor design and architecture. Doing too much and blocking the event loop, memory leaks, using too much frontend code to poorly mimic native browser features like new tabs and back buttons, uncaught exceptions that stop the javascript thread and leave the page stuck, etc.

Re: Angular 9.0

#97

Post by erulabs »

acemarke wrote: post #68
randall wrote: post #63

Earlier quoted context omitted.

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 sim…

Hi, I'm a software engineer.

Thank you for your work on Redux - I think it's fantastic!

Lots of hate in this thread, but React/Redux are great, even if that somehow makes me an imposter or a hipster or whatever the tools I use somehow say about me.

Re: Angular 9.0

#98

Post by Bahamut »

dnautics wrote: post #84
_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…

I can put a junior in react and be fairly sure that nothing too crazy will happen. I can't say the same for angular.

I wouldn’t say the same no matter the domain - junior devs can and will surprise you, and because React gives you less guardrails for app architecture, it likely has the potential to go far worse.

Re: Angular 9.0

#99

Post by ErikAugust »

filoeleven wrote: post #85
dfsegoat wrote: post #66

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.

AFAICT the upgrade path is still the same (0) and...it looked pretty painful when I first looked at moving from 1.x to 2. I maintain a sizable 1.x codebase and am deciding what to move to, since 1.x is dead next year. I just don’t see a good reason to go to 2+. It’s a different framework. All of the UI libraries we built upon (ng-grid, angular-ui) are either gone or different enough that we will have to redo all of o…

AngularJS is dead next year, but really that doesn't stop you from using it indefinitely. Of course it can be fun to rewrite everything.

Re: Angular 9.0

#100

Post by jb300 »

kumarvvr wrote: post #82
kabes wrote: post #77

Earlier quoted context omitted.

I've used both for non-trivial apps. I find angular heavily over-engineered. The problem is not just the learning curve, but the fact it becomes almost impossible to do anything the framework authors didn't envisage. React is just plain functions so you can do whatever you want, it never got in my way. Now, if angular would prove substantially better in terms of performance or maintainability or so, that might've bee…

I am curious. I have never used Angular or React seriously. But I have an upcoming project where I have to use an external HTML Canvas library. Would you suggest I go with Angular or React? It's a fairly complex project, involving user based label designs, data manipulation, etc. I am API based server and a heavyweight front-end.

Have used Angular2 since alpha for a big project. Switched to React + Typescript for the next project. In my opinion React + Typescript is the way to go, especially if you'll use external libraries.
Post reply on HN