Live data from Hacker News

Criticisms of Angular

leanpanda.com

21–30 of 150 posts

Re: Criticisms of Angular

#21
They announced recently that there will be an easy Angular 1 to Angular 2 migration path.[1]

I think Google is getting blowback from the "worse is better" crowd that have supported the meteroic rise of c, php and mongodb. Specifically, the "worse is better" belief that:

"There is a point where less functionality ('worse') is a preferable option ('better') in terms of practicality and usability." [2]

reminds me of his criticism of "excessive" features in Angular, even though those features are there for a reason.

Usually, what happens with "worse is better" is that when people start missing key features, a bunch of bolt on pre and post processor tools show up to add features (e.g linters, "strict mode",Mongo migration tools) that weren't needed in the more complete solution.

1.http://news.softpedia.com/news/google-releases-guide-on-how-...

2.https://en.m.wikipedia.org/wiki/Worse_is_better [fixed]

Re: Criticisms of Angular

#23

They announced recently that there will be an easy Angular 1 to Angular 2 migration path.[1] I think Google is getting blowback from the "worse is better" crowd that have supported the meteroic rise of c, php and mongodb. Specifically, the "worse is better" belief that: "There is a point where less functionality ('worse') is a preferable option ('better') in terms of practicality and usability." [2] reminds me of his…

[deleted]

Re: Criticisms of Angular

#24
post #9

Earlier quoted context omitted.

I like Angular's DI. It makes it easy – to me, but YMMV - to organize my thoughts and my code.

Fair enough. It's probably a matter of taste to some extend. I generally don't like too much structure unless there are clear benefits and DI doesn't seem to hold up on that scale. The problem it's solving has traditionally been solved with a dozen global variables. And while the purists may scuff at this, I find that in practise it's never an issue in otherwise well structured code.

Too many people reach for DI first where some quiet time with a pencil and paper could produce a much better design that doesn't need a DI framework.

Re: Criticisms of Angular

#25
post #13

Earlier quoted context omitted.

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 a…

Sure you can. And as I said, I'm not a big angular lover. In fact we used Backbone for REST in it, because of shortcomings of the $resource at the time.

And flux is great and React-first, but it's not technically a part of React. And it is also great, having a choice is usually a good thing.

Still I'm skeptical when people are happy just because they moved from angular to react. Or from any X to Y really. Usually the gain comes more just from rewriting things with better understanding of the project and from more established team. No one does A/B studies on it, right?

Re: Criticisms of Angular

#26
I haven't tried Angular yet but have built applications in React. In my opinion, frameworks like Angular suffer from a fundamental problem, that, it is almost impossible to gauge the problems of a new design unless you have a built a medium - large scale application with it which is very hard when you are just experimenting. There might be few heuristics, few rule of thumbs one can follow but still it will be hard to see if the ease - effort ratio will make the framework worthwhile. You can make things too "magical" and also too "worthless".

I guess that's why everyone complains that it is easier to build a Todo application in Angular but the troubles grow as you grow bigger. The reason why React is successful might be they did get a chance to experiment the architecture on their own things before releasing it to the public.

Re: Criticisms of Angular

#27

I haven't tried Angular yet but have built applications in React. In my opinion, frameworks like Angular suffer from a fundamental problem, that, it is almost impossible to gauge the problems of a new design unless you have a built a medium - large scale application with it which is very hard when you are just experimenting. There might be few heuristics, few rule of thumbs one can follow but still it will be hard to…

I've never understood any comparison between React and Angular. To me it seems like trying to compare a slick car to a fancy car garage. They try to solve quite different problems, right?

Re: Criticisms of Angular

#28
OT: why are they using "BazaarJS" in the titles of both this and the post they're linking to but "BazarJS" everywhere else in the articles?

Re: Criticisms of Angular

#29
post #18

"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.

Factory is just a function. It can easily instantiate and return singleton. You just call it instead of using `new` on it at the place of use. It's probably not very nice from philosophical standpoint but it can have its merits.

Re: Criticisms of Angular

#30
So, they trot out the same tired arguments against Angular that people have been making since the beginning, and this makes the front page where people engage in serious discussion about it?

Did I miss some subtle novelty about this post, or is Angular ennui just that popular on HN?

Post reply on HN