Live data from Hacker News

Angular 9.0

blog.angular.io

101–110 of 308 posts

Re: Angular 9.0

#101
post #28
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…

I have the exact opposite opinion. React is the only sane way to do web development. All other approaches are deeply flawed by either relying on imperative mutations of the DOM instead of clean declarative code, or by relying on ugly templating syntax and data attributes instead of just using JS basic constructs like react. The power of react is just at its beginning, as we can see with things like react-three-fiber that was coded in a weekend initially and which is unthinkable in any other framework.

Edit typo

Re: Angular 9.0

#102
post #28
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…

Wow! such a strong opinion warrants some more justification.

Having used both Angular (since 1.0) and React (only recently), it's obvious why React is more popular. Any decent engineer can be productive in React within a day since the concepts are so intuitive and simple. With Angular, if you don't really know how things work, you are going to struggle a lot for a while.

While i can't speak for the rendering performance, the design itself is definitely elegant and not built for "code monkeys" but real engineering productivity

Re: Angular 9.0

#103
post #90

Earlier quoted context omitted.

This couldn't be more wrong. The team does a great job handling upgrade paths post 2.0. First off, Angular versions post 2.0 are nothing like AngularJS/1.x -> Angular/2.0. They are much more incremental and even the two times the entire renderer has been re-written it was an incredibly gradual process over multiple major versions with seemingly few changes to component and template APIs. Second, upgrading between Ang…

> This couldn't be more wrong. The team does a great job handling upgrade paths post 2.0. The problem isn't how it's handled or how incremental it is, it's that there are so many upgrades with breaking changes, at least that's what they're communicating to me with their version numbers. There's also the lack of any real LTS versions I mentioned, 18 months doesn't cut it. > They are much more incremental and even the…

Fair enough, but I'm not sure you understand how nice schematics are. You can use them for a lot of things, but one nice use case is essentially update migrations. You literally just run `ng update @angular/cli @angular/core` and a majority of the time you're good to go...

Re: Angular 9.0

#104
post #28
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…

If for you extrapolating types trying to fit a square into a circle every variable declaration and having 10 lines of decorators per file means less boiler-plate then yes angular is the better framework.

Re: Angular 9.0

#105
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 have the exact opposite opinion. React is the only sane way to do web development. All other approaches are deeply flawed by either relying on imperative mutations of the DOM instead of clean declarative code, or by relying on ugly templating syntax and data attributes instead of just using JS basic constructs like react. The power of react is just at its beginning, as we can see with things like react-three-fiber…

Exactly! JSX is much easier to use compared to angular templating.

Re: Angular 9.0

#106
post #90

Earlier quoted context omitted.

This couldn't be more wrong. The team does a great job handling upgrade paths post 2.0. First off, Angular versions post 2.0 are nothing like AngularJS/1.x -> Angular/2.0. They are much more incremental and even the two times the entire renderer has been re-written it was an incredibly gradual process over multiple major versions with seemingly few changes to component and template APIs. Second, upgrading between Ang…

> This couldn't be more wrong. The team does a great job handling upgrade paths post 2.0. The problem isn't how it's handled or how incremental it is, it's that there are so many upgrades with breaking changes, at least that's what they're communicating to me with their version numbers. There's also the lack of any real LTS versions I mentioned, 18 months doesn't cut it. > They are much more incremental and even the…

React has some really painful breaking changes over the last 3 years - Angular did breaking changes in a far more user friendly way. The last breaking change that happened from 16.8 to 16.9 partially ended up resulting in us calling bankruptcy on our main app and helped make the decision easier to rewrite it from scratch on a team where the core members who worked on the app have over 70 years of experience amongst 4 devs.

Re: Angular 9.0

#107
post #40

Earlier quoted context omitted.

It reminds me of the whole .NET ecosystem. All of these custom magical special ways to do everything, compared to ‘dumb’ setups like node/ruby/go where the actual logic is just right there in front of you And every release .NET just keeps moving closer to the dumb systems. Simple and raw is good, keep the magic away

I am really glad there are other people who think this way. I am experienced with Python/JS/Ruby web app development models and recently had a look at ASP.NET Core web api projects. The amount of complexity is mind boggling. I mean, look at Flask in Python. Or even Expressjs in Node, why can't Microsoft come up with a simple framework that can run well on the .NET runtime? I am a huge fan of C#, having used it for De…

Is something like Nancy [0] close to what you're after? I've not used it myself because I prefer the structure of the full approach but from my extremely brief interaction with Express in Node it seems similar?

[0]: https://github.com/NancyFx/Nancy

Re: Angular 9.0

#108
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.

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.

I haven't used the more recent version of Angular so not sure what their "stack" is, but doesn't `create-react-app` take care of much of that?

Re: Angular 9.0

#109
post #98

Earlier quoted context omitted.

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.

Well obviously they'll be CR'd. If you stick to prop drilling and functional code there's far less you can do abjectly wrong.

Re: Angular 9.0

#110

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…

What is with this bazaar conviction that classes are bad?
Post reply on HN