Why Angular Made Me Quit Web Dev • Hacker News Board

Re: Why Angular Made Me Quit Web Dev

#11

Post by draluy » Mon, Nov 05, 2018, 1:24 PM UTC

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

I find it very bloated. I spend so much time waiting on the compiler and writing boilerplate code (as opposed to actual features), that I try to avoid it when I can.

I really prefer Vue, because it gets out of my way when declaring services or making modules etc.

Re: Why Angular Made Me Quit Web Dev

#12

Post by monkeynotes » Mon, Nov 05, 2018, 1:29 PM UTC

jordache wrote: post #10

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

Why do you take to stock this random dude's rant? It's all just verbal diarrhea. There are legit criticisms of Angular no doubt. This article is not that

This is why I am asking other "random" developers. I don't take what this guy says as gospel, but it is a voted article on a source of information that I both engage with and somewhat trust.

Re: Why Angular Made Me Quit Web Dev

#13

Post by lsiunsuex » Mon, Nov 05, 2018, 1:29 PM UTC

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

I rather like Angular. We started our project on Angular 5, recently upgraded to Angular 6 and we're holding off on Angular 7 just because PrimeNG 7 isn't ready yet.

(upgrading isn't why I like it)

I agree that ng build --prod finds different errors then ng serve -o does but we build once a day and fix them when we find them, before deploying to QA. We've also learned pretty well when a bug in build might be caused (usually not declaring a property properly or wrong type or whatever)

Actual development is pretty easy once you learn the concepts. Documentation, training, tutorials are good IMO also.

The only complaints I have are PrimeNG (our CSS framework) has a LOT of bugs, is sometimes poorly documented and the built in components are often lacking; when they are, we extend them and add what functionality we need ourselves.

I don't want to cause a React vs Angular thread - but compared to React and the 100s of ways to get a project built, I prefer to use Angular - here is the MVC and go type approach.

Re: Why Angular Made Me Quit Web Dev

#14

Post by monkeynotes » Mon, Nov 05, 2018, 1:30 PM UTC

draluy wrote: post #11

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

I find it very bloated. I spend so much time waiting on the compiler and writing boilerplate code (as opposed to actual features), that I try to avoid it when I can. I really prefer Vue, because it gets out of my way when declaring services or making modules etc.

React + Redux is pretty famous for boilerplate, so I guess I can continue to look forward to feature friction.

Re: Why Angular Made Me Quit Web Dev

#15

Post by korynunn » Mon, Nov 05, 2018, 1:35 PM UTC

jordache wrote: post #3

korynunn wrote: post #2

I associate with this so much it hurts. I have wasted thousands of my employers dollars just waiting for this pile of shit to compile or run. If you like light, fast, opinion free UI tools, maybe give my module fastn a go: https://GitHub.com/korynunn/fastn

sarcasm at the end there? ditch a product that has a global community, built legit enterprise scale apps with, for a personal project found on github?

No this is my module that I've used to build enterprise apps with.

I've used both for years, feel free to critique fastn when you've tried it for a week.

Re: Why Angular Made Me Quit Web Dev

#16

Post by korynunn » Mon, Nov 05, 2018, 1:37 PM UTC

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

Have used it for a bit over a year now. Hate it. Horrible for productivity, horrible to debug, horrible performance, horrible bundle sizes.

Re: Why Angular Made Me Quit Web Dev

#17

Post by korynunn » Mon, Nov 05, 2018, 1:39 PM UTC

korynunn wrote: post #16

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

Have used it for a bit over a year now. Hate it. Horrible for productivity, horrible to debug, horrible performance, horrible bundle sizes.

I forgot to add: Horrible to test.

Re: Why Angular Made Me Quit Web Dev

#18

Post by duckMuppet » Mon, Nov 05, 2018, 1:51 PM UTC

ssharp wrote: post #9

Not the point of the article, but how exactly did the iPhone's utility flatline because they removed the headphone jack and how is a headphone jack a "vital" feature, considering the rise in popularity of blueetooth headphones and the fact that the iPhone ships with the 3.5mm dongle?

Mom: "What are you doing on your computer?"

Child: "What's a computer...."

Additionally, he must've missed the last 20+ years after Apple moved away from the ppc chip.

Subsequent editions of os x after were always removing great tools, then rebranding and repackaging them to sell as a new feature. Up until you had to pay for the dev tools..

The best has been iDevices though. Premium price through artificial resource scarcity.

Ask that being said, the author and like the type who instead of looking for a better product, would look to govt and regulations for Apple, and the web dev sphere. In the name of fairness I'm sure.

Re: Why Angular Made Me Quit Web Dev

#19

Post by jbob2000 » Mon, Nov 05, 2018, 2:16 PM UTC

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

Currently rewriting an app from AngularJS to Angular 7.

Biggest pain point is doing stuff outside of the angular framework. Interacting with the browser’s History API is annoying, angular splits this functionality over a few disparate modules and it’s heavily suggested you do not call the raw APIs directly, but instead deal with the tangled mess angular provides.

I had some pains when I first got started, but that was because I wasn’t doing it the “angular way”. If you find you’re writing too much code and it feels like “low-level” code, you’re probably doing it wrong. I spent a lot of time wrangling Observables and async pipes before I found patterns that were simple and met my needs.

Re: Why Angular Made Me Quit Web Dev

#20

Post by ahayter » Mon, Nov 05, 2018, 2:30 PM UTC

monkeynotes wrote: post #7

Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??

Got a new full-time gig working on an Angular 5 app about 3 months ago (they're behind in the upgrading to 6/7 for god knows why). Coming from working on an angularjs app for around 3 years.

I'm unimpressed with essentially the entire framework. It feels over engineered and overly complex with little benefit. Note that I'm saying it feels that way, maybe at some kind of scale this is very helpful, the codebase I'm working in is about 150k sloc.

The biggest gripe for me is how unintuitive it is to compose and reuse bits of UI. Having written almost no React, and absolutely no React professionally, I understand how to compose react components and the basic patterns for communicating between them. It's just not as easy in Angular, so for the most part it just doesn't happen (at least with the devs I'm working with). Patterns such as render props, HOC, stuff like that is not straight forward in Angular. I'm probably not thinking in the "Angular" way or something.

The dependency injection patterns that Angular is so fond of is something I'm not enthralled with as well. It made more sense in angularjs since es2015 modules weren't prevalent at the time, it really solved a problem there. I don't think it's as helpful in Angular now, and is yet another framework specific thing you're going to have to grasp at a decently deep level.

I work right next to another dev that was hired about a month before me. He's coming from writing React for the last couple of years, and angularjs was the first SPA framework he ever learned. He is constantly cursing how Angular does just about everything, he's not a happy camper.

If I was calling the shots today I would not use Angular for my SPA framework.