Hacker News new | ask | show | jobs
by davide_v 1623 days ago
Totally correct to discontinue the old AngularJS imho. Google, years ago, made one of the best choice adopting TypeScript for its new framework, Angular. I used to code in both AngularJS and Angular, and the improvement between the two is huge, thanks also to TypeScript. I'm a big Angular fan, even if I tried React, I highly prefer Angular for being more strict, complete and imho more suited for very big projects.
3 comments

> I'm a big Angular fan, even if I tried React, I highly prefer Angular for being more strict, complete and imho more suited for very big projects.

I agree, I just moved us to Angular 13 and I love every second of it.

I've worked on React projects but will take Angular any day of the week.

Having worked with both, react much much less, but more recently, I find react just simpler to get stuff done with. Angular has a pretty rigid structure that I felt required more files and code (even if you just use the ng CLI to code gen the initial component or service) to do the same thing.

Obviously the batteries included nature of Angular is nice. But otherwise I felt less burdened by the amount of code I need to write and read in react.

RxJS is nice though and testing via dependency injection as long as your app isnt a horrible mess and has good decoupling.

Imo react is simpler to get stuff done with up until a certain point. Every large react project I’ve contributed to, or adopted, had the same overhead you described of Angular. Further, each had built custom abstractions due to the nature of how integration works with react. Some apps were fine, some had 1000+ line state files, 1000+ lines of hooks management before a render, weird ways of using context or passing props.

Today we still prototype mostly with react. It’s easier to staff junior devs around and empowers them when it comes to trivial logic with cool UX.

Any large scale work, or prototypes going to prod, do so with Angular. Where we’re confident in the Sr level engineers writing that code.

I also just finished migrating from AngularJS to Angular13. I have to say, it was very straightforward and not especially difficult. And going from a custom webpack setup to the angular CLI is pretty amazing.
I'm enjoying Angular development too, although the Angular Material library is... not great. Lots of corner cases that just don't get enough attention.
We use PrimeNG and I would highly recommend it.

It's under MIT also which is a bonus depending on your use case.

https://www.primefaces.org/primeng/showcase/#/

Can you clarify what you mean by "more strict"? I've been using React since before Redux existed and while these days I don't think there is any need for a state library anymore I of course agree that Angular is more complete as one of the first decisions you make when starting a React project is which routing library to use (e.g. react-router or reach-router, or if you want an integrated solution, remix or next) and what to do about network requests (e.g. react-query or one of the many GraphQL libraries).

I also think it's worth pointing out that people have very different understandings of what "very big projects" are. I think you mean projects with many different people working on it, in which case I agree, but often people misinterpret these statements thinking that their 1-5 person team working on a web app is a "very big project" because they have a million users.

AngularJS seemed to be the last well supported fronted library that let me just write JavaScript, and not need to pull in the entire node ecosystem just for making a simple website.

It's insane to me that websites need to be compiled these days. My websites mostly consist of an index.html and a code.js, and then unzipping whatever goofy template into the js, css, images folders etc. I feel like requiring a fluent understanding of the entire node ecosystem build even the simplest websites is a big enough hurdle that a lot of enthusiastic new people are just going to give up and do something else.