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

151–160 of 308 posts

Re: Angular 9.0

#151

Post by woodpanel »

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…

Having ported some Angular SPAs from 1.x to 2++ I have to say: Looked more painful at the onset, was actually quite easy in the end.

Having used React for some years now, I have to say: I wouldn't compare the two. React's atomic ecosystem is perfect if your stack of tools you embed doesn't grow too large.

However as soon as you want the feature set Angular provides out of the box IMHO you're screwed.

Re: Angular 9.0

#152

Post by crubier »

izietto wrote: post #149
crubier wrote: post #145

Earlier quoted context omitted.

You are right indeed, but from a developer point of view at that point you could be using a react based framework and your experience would be the similar to vue with JSX. Render functions returning JSX is the key brilliant idea invented by react and the fact that vue adopted it just proves the point even more: React or the ideas at the core of react are not the mistake of the last decade but the blessing of the last…

> from a developer point of view at that point you could be using a react based framework and your experience would be the similar to vue with JSX It will not, because Vue has a better integration with the data source (Vuex) and a better integration with the routing (Vue Router) I mean, I agree that React is an awesome framework implemented upon great design ideas (pure functions and plain JS templates), but it has i…

For routing react-router is just perfect. And for data source/state management there is plenty of choice, I use Apollo for global state/data source and useState for small state full interactions, I can’t see how it could get simpler.

But whatever floats you boat really, the point is that the nice part of vue are inspired by react anyway. I wish the two community merged, to be honest, I see no point in dividing for such small differences.

Re: Angular 9.0

#153

Post by aabbcc1241 »

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.

Stencil provides similar experience to React, plus Stencil compiles every component into typed web component, so it works with other frameworks as well.

Re: Angular 9.0

#154

Post by DonHopkins »

tannhaeuser wrote: post #112
crubier wrote: post #101

Earlier quoted context omitted.

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…

I'm not a React hater (in fact, I like it a lot when it fits ) but I think when people criticize React, they're actually after the one-size-fits-all attitude displayed in comments such as yours. No, React is clearly not "the only sane way of doing web development" considering the web hosts many types of markup applications, the most successful ones predating React by decades.

Off topic: I've always meant to ask you: Is your name a Blade Runner reference, or are you a user something called "Tannhae"? ;)

https://en.wikipedia.org/wiki/Tears_in_rain_monologue#Tannh%...

https://en.wiktionary.org/wiki/%E6%8E%A2%E6%B5%B7

Re: Angular 9.0

#155

Post by mattlondon »

Phenix88be wrote: post #136

After 2 years of Angular madness I will send my resignation and I hope I will never work with it again. My app is a big stack of workaround stuff that might break anytime. Because that is how angular work. Some stuff work in a context and doesn't in an other. Nobody's know why ! They have so much issue on Github that they need a bot to close them after a while. They hope the bug disappear by himself ?

Do you have any examples? I've been doing Angular2+ apps for years and have not experienced this.

Re: Angular 9.0

#156

Post by mattlondon »

gitgud wrote: post #88

The only thing I like about Angular is the dependency injection of services. Having "services" managed for you and just picking and choosing what you want is pretty nice. What I don't like is the verbosity and boilerplate... here's 2 examples: - Routing boilerplate is convoluted and time consuming. I think Nuxt.js has a much nicer implementation of SPA routing, where the filesystem is used to map the routes. - Angula…

Another benefit in my mind is that Angular is "batteries included" - you get everything you need in a single library, e.g. routing is a big one.

From what I understand of React, you need to pick and chose the libraries (and versions of those libraries!) to use for your app, and then keep the versions of all the different libraries up-to-date and in sync with each other. Sounds like a maintenance nightmare.

Re: Angular 9.0

#157

Post by johnnyAghands »

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.

A lot of enterprises hiring juniors on the cheap actually thought of it in the opposite way. They saw Angular's rigidity as some sort of safety rails to help guide developers in the rightish direction. They thought React was the Wild Wild West of JS land ;D No manager got fired for choosing Angular. If only

Re: Angular 9.0

#158

Post by brailsafe »

kroltan wrote: post #34
brailsafe wrote: post #25

Earlier quoted context omitted.

I think that's pretty well correct, but my preference has been the opposite in terms of more concepts vs cognitive complexity. I find that to do the same stuff with react and redux and so on, you end up decoupling and abstracting in such a way that the 5 or concepts in something like Angular or Vue end up being a more manageable mental model. In the sense that the main purpose of React is lost in the weeds of trying…

I have found good success with React + RxJS, in fact. They have some overlap, but with the benefit of interop outside React, and Rx is excellent at both message-passing-style events, as well as general-purpose "data binding". And the total load is still in my perspective smaller than Angular. I have never even casually used Vue (I've since switched to gamedev as a profession), so I cannot comment on it, but from a cu…

That's a curious suggestion. I've never taken a serious look at RxJs, but I've used obsevables in android so might do that. Vue is like React but just enough separation to get all the benefits that I find in composition as well as the templating and stuff from Angular. How did you make the switch to game dev?

Re: Angular 9.0

#159

Post by thallukrish »

I have spent a lot of time in Angular 2 and later in Angular 6. I had later switched to plain java script and used requireJS to modularize. I have my own orchestrator to route events like a pub-sub. HTML5 + CSS + plain JS is good enough for most simple UI.

Re: Angular 9.0

#160

Post by Phenix88be »

mattlondon wrote: post #155
Phenix88be wrote: post #136

After 2 years of Angular madness I will send my resignation and I hope I will never work with it again. My app is a big stack of workaround stuff that might break anytime. Because that is how angular work. Some stuff work in a context and doesn't in an other. Nobody's know why ! They have so much issue on Github that they need a bot to close them after a while. They hope the bug disappear by himself ?

Do you have any examples? I've been doing Angular2+ apps for years and have not experienced this.

I had many, but here is the first I can remember correctly :

I have a backendService that use the httpClient; it's a wrapper that automate stuff to make API request. I guess it's pretty common. I have a provider for APP_INITIALIZER. It can use the HttpClient but not the backendService. The backendService work everywhere else of course.

Post reply on HN