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

251–260 of 308 posts

Re: Angular 9.0

#251

Post by grok22 »

qwerty456127 wrote: post #190
grok22 wrote: post #55

Earlier quoted context omitted.

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. Th…

> decided to learn Dart and AngularDart Why use anything but Flutter if you choose Dart?

Flutter is not yet approved for web application development, isn't it? In any case, just experimenting and learning new things.

Re: Angular 9.0

#252

Post by madoublet »

Phenix88be wrote: post #193
JoeNr76 wrote: post #170

Earlier quoted context omitted.

I've been doing Angular for 5+ years now. I think you might be using it wrong because I never experienced anything like that.

I m pretty sur the 2500+ issues on github are not all people using Angular wrong. Yet I agree, a lot of things in my project is wrong and maybe blaming the framework for the mess is too easy. But I really do not enjoy working with Angular. Also, learning to use RxJS was a painful experience full of frustration.

I agree with you 100% here. I have been working in Angular for a long time and feel like I have a pretty strong understanding on how it works. Like you, I will not build another app with Angular (or any framework for that matter). I don't think I encountered as many bugs as you have, but I have spent too much time trying to figure out how to do it the Angular way or the RxJS way. With modules, web components, promises, and async/await, I feel like you can now write very clean code with just JS. So, that is what I am going to do going forward.

Re: Angular 9.0

#253

Post by IggleSniggle »

kls wrote: post #225
ghego1 wrote: post #207

Earlier quoted context omitted.

Your argument is flawed with a very opinionative starting point, which is that Angular wouldn't provide a solid foundation. This is, at the very best, very debatable. In my experience, it's the very opposite. Angular gives you very solid foundations as it's a proper framework that ships everything you need to build scalable apps. So you start from something small, and as you grow you know you can do so without rethin…

They are not people with more experience you are appealing to authority. The cold hard truth is that Angular got it so wrong the first go around that they had to completely rewrite the framework. The very reason was that a lot of the early guys where just out of school and built a framework on theory. If you contrast this with React, guys in the trenched trying to build applications at scale for FB, they where built…

...well...on THIS day there is said tooling. In Angular 9.

Re: Angular 9.0

#254

Post by machello13 »

node-bayarea wrote: post #246
Pigo wrote: post #244

Earlier quoted context omitted.

Almost every problem I've seen with Angular involve people not knowing how to implement features correctly or using it for what it wasn't meant to be used for. You know, the same problems people have with all frameworks.

Use things like Svelte. It's a framework that lets you hack. You don't need 'best practices'.

why in the world would I want a framework that lets me hack?

Re: Angular 9.0

#255

Post by bdcravens »

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 ?

What framework would you use to avoid those workarounds (or others in different parts of your app)?

Re: Angular 9.0

#256

Post by kls »

IggleSniggle wrote: post #253
kls wrote: post #225

Earlier quoted context omitted.

They are not people with more experience you are appealing to authority. The cold hard truth is that Angular got it so wrong the first go around that they had to completely rewrite the framework. The very reason was that a lot of the early guys where just out of school and built a framework on theory. If you contrast this with React, guys in the trenched trying to build applications at scale for FB, they where built…

...well...on THIS day there is said tooling. In Angular 9.

This is the most comprehensive document I can find on debugging in 9 and I still do not see a way to set a breakpoint in say a loop declared in a template. I may be missing something as I have not worked on an Angular project in probably 6 months. But I don't see template debugging I see being able to get reference to a component and then manipulate said component via dev tools.

https://juristr.com/blog/2019/09/debugging-angular-ivy-conso...

Re: Angular 9.0

#257

Post by IggleSniggle »

crubier wrote: post #231
Cthulhu_ wrote: post #202

Earlier quoted context omitted.

"Built on shaky grounds" needs a citation and additional explanation. I mean I hear what you're saying, but Angular is an opinionated framework whereas React is not, and many people end up reinventing the wheel (or an application framework) in the process. There is value in being opinionated.

The churn between angular versions, stemming from the limitations and inconsistencies of two way data bindings and others, are what I mean by «shaky grounds». Yes there is value in being opinionated, but it is less risky to decorrelate the opinion from the foundation. There are opinionated frameworks built on top of react and it is very nice like this. But react itself should not be opinionated.

I'm not sure what churn you are talking about, unless you mean the Angular 1 - Angular 2+ split?

ng update is ridiculously easy, and the automatic code rewriting is generally sensible and easy to follow. When there are breaking changes, Angular takes care of the modifications for you. Generally I've felt like those changes resulted in a better expressed codebase (eg RxJS syntax improved massively from 5 to 6, lazy loaded routes are expressed with arrow functions now, etc).

I assumed the React community was also migrating versions with codemods, but maybe React does not introduce any breaking changes?

Re: Angular 9.0

#258

Post by rsinger87 »

Huge thanks Angular team. A few years ago, my team desperately needed to pick and run with a frontend framework. After a couple months to learn the Angular fundamentals, we haven't looked back. We find the framework to be extremely intuitive and flexible enough to handle any scenario we've encountered. The productivity wins have been enormous. We have about a dozen apps and anyone on our small team can jump into any project and contribute. I can't imagine how fractured our knowledge would be if we had to stitch together multiple libraries and come up with our own constructs.

Re: Angular 9.0

#259

Post by acemarke »

erulabs wrote: post #97
acemarke wrote: post #68

Earlier quoted context omitted.

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.

Thanks, and you're welcome!

I obviously didn't _create_ Redux, but I'll take a decent amount of credit for helping keep it relevant over the last few years (docs work, blog posts, answering questions, React-Redux updates, Redux Toolkit).

I'll say up front that it's definitely not as "necessary" as it was early on and that there's lots of other great alternatives out there, but yeah, I don't get the recurring waves of "I hate Redux" that seem to pop up on Twitter every few months.

FWIW, I talked about some Redux usage stats and where it fits in compared to other options in my "State of Redux" talk at Reactathon last year:

https://blog.isquaredsoftware.com/2019/03/presentation-state...

Looks like I should get to do an updated version of that talk later this year.

Re: Angular 9.0

#260

Post by s_y_n_t_a_x »

kls wrote: post #234
s_y_n_t_a_x wrote: post #162

Earlier quoted context omitted.

Or you know, use Redux because the boilerplate is gone... https://redux-toolkit.js.org/ You don't have to create actions or constants anymore, you just create your reducer functions and selectors, then use hooks to select and dispatch in your components. Never got why people took up a completely different paradigm just because they couldn't figure out how to reduce their boilerplate...

Or use XState as Redux is only a half implementation of a state machine. It get's the job done but a state machine gives you far more structure and comprehensibility around state management. https://github.com/davidkpiano/xstate

Which is great because you don't need a full state machine.

React can be that other half...

Post reply on HN