Criticisms of Angular • Hacker News Board

Re: Criticisms of Angular

#11

Post by nioufe » Wed, Sep 23, 2015, 11:21 AM UTC

While the author makes some fair point about angular's weirdness. He fails to understand that many design choices where made because javascript and js libraries were not as advanced as today.

For example the module system is made so because at the time, amd, browserify and ES6 modules were not ready.

And the main point of angular 2 is not to remake angular because it was weird, it is to adapt it to new technologies.

Re: Criticisms of Angular

#12

Post by yogsototh » Wed, Sep 23, 2015, 11:23 AM UTC

stuaxo wrote: post #10

This is all true, but it is still one of the best options for making websites, onwards and upwards !

We use reagent with success. We still have some legacy code in Angular. Each time we need to change something in that old code, it reminds us how Angular has done a lot of things wrong.

We often qualify Angular as the J2EE of the front.

Re: Criticisms of Angular

#13

Post by fridek » Wed, Sep 23, 2015, 11:27 AM UTC

apeacox wrote: post #8

Antwan wrote: post #3

"With the next article we’re going to introduce you to React JS, [...] that have won us over entirely." How can you take the article seriously with that kind of conclusion.

why?

Because React solves only the directive part of Angular? I'm not saying it's great BTW, but comparing React to Angular is silly. That's like saying you chose lodash.js over Angular.

Re: Criticisms of Angular

#14

Post by protonfish » Wed, Sep 23, 2015, 11:39 AM UTC

He missed so much. How about non-standard invalid HTML? Breaking all searchability and accessibility? Encouraging voodoo coding?

Re: Criticisms of Angular

#15

Post by kcorbitt » Wed, Sep 23, 2015, 11:39 AM UTC

fridek wrote: post #13

apeacox wrote: post #8

Earlier quoted context omitted.

why?

Because React solves only the directive part of Angular? I'm not saying it's great BTW, but comparing React to Angular is silly. That's like saying you chose lodash.js over Angular.

This was probably a valid observation two years ago, when the React story on state management was "bring your own solution." But these days, although it's technically a separate project, Flux is the de-facto state management solution that a React-first webapp will use. There are lots of competing implementations (I use redux) but my point is that you'd be hard-pressed to find an app written in Angular that couldn't also be written using React+Flux. Of course the architecture is going to look different, but you can certainly get to the same place.

Re: Criticisms of Angular

#16

Post by the_mitsuhiko » Wed, Sep 23, 2015, 11:41 AM UTC

fridek wrote: post #13

apeacox wrote: post #8

Earlier quoted context omitted.

why?

Because React solves only the directive part of Angular? I'm not saying it's great BTW, but comparing React to Angular is silly. That's like saying you chose lodash.js over Angular.

> Because React solves only the directive part of Angular?

I can't say I miss anything from angular in React. If anything it's good that React does not try to go too far down the rabbit hole. Which particular functionality is absent in React that you need?

Re: Criticisms of Angular

#17

Post by eyko » Wed, Sep 23, 2015, 11:46 AM UTC

fridek wrote: post #13

apeacox wrote: post #8

Earlier quoted context omitted.

why?

Because React solves only the directive part of Angular? I'm not saying it's great BTW, but comparing React to Angular is silly. That's like saying you chose lodash.js over Angular.

Have you been paying attention to the React ecosystem in the past... year or so?

Re: Criticisms of Angular

#18

Post by fridek » Wed, Sep 23, 2015, 11:51 AM UTC

"I’m not joking: we were perfectly able to get by in one of the Angular projects developed internally — consisting of around 200 Javascript files and a total of around 10,000 lines of code — using only factories."

Funny, I could agree this is true for providers or services. Factories however can't be used for singletons, so I'd rather not know how they implemented shared state and utils.

Re: Criticisms of Angular

#19

Post by neals » Wed, Sep 23, 2015, 11:52 AM UTC

I work as a JS contractor on large custom e-commerce configurators. In the last few months I've learned that Angular is not built for large custom e-commerce configurators. Just my 2c /

Re: Criticisms of Angular

#20

Post by Loque » Wed, Sep 23, 2015, 11:53 AM UTC

protonfish wrote: post #14

He missed so much. How about non-standard invalid HTML? Breaking all searchability and accessibility? Encouraging voodoo coding?

This was the deal breaker for me when first looking at Angular - loose coupling, progressive enhancement, accessibility and keeping code in its appropriate layers seemed to get thrown out for an attitude that everyone has JS running... it felt like a return to the days of Flash.

I could ramble for a long time about it, anecdotally; I have peers who use (and seem to enjoy using) Angular (all .net devs), and others who point out its flaws (front-end architects). I find it a very interesting discussion point.