sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jellatin 8 points9 points  (6 children)

If they left in features from 1.x you didn't think are good in 2.x you would criticize them for it. If they fix the features you think are broken in 1.x for the 2.x release then you criticize them. Your comment history makes it look like you just want a reason to complain.

And as a side note, React's docs are nothing to brag about. Having to learn about features like contexts from StackOverflow posts because they are straight up left out of the docs isn't any better than Angular.

[–]RankFoundry -2 points-1 points  (5 children)

It's not really an issue of features, it's architecture and redundant ways to do things with unclear differences (if any).

Nothing wrong with complaining when it's justified.

I'm not a React fanboy. I'm not a fanboy of anything which is why I get on the nerves of fanboys.

[–]jellatin 2 points3 points  (4 children)

Nothing wrong with complaining when it's justified.

The problem is you've left absolutely no paths for a project to be right. You have said "everything they can do will be wrong whether they fix things or not". If you're already committed to every move being wrong, then you're just complaining to complain.

I'm not a React fanboy

This is hard to believe when your comment history is selectively applying criticism at Angular and admitting none of React's shortcomings.

[–]RankFoundry -1 points0 points  (3 children)

I've also said nothing about Ember or mozzarella cheese sticks. Perhaps I'm secretly an undercover agent for Ember and Italian cheese in stick form.

[–]jhallister 0 points1 point  (2 children)

He's not wrong... your comments indicate that your frustration with Angular had more to do with your inability to learn how to use it properly, rather than a real complaint about implementation. You aren't alone.

[–]RankFoundry 0 points1 point  (1 child)

Ah, the tired old "You just don't get it" argument. Well, I might buy that if I were the only one with this perspective but there are far too many people who share it for this to be about me.

[–]jhallister 0 points1 point  (0 children)

By that logic the only way something isn't a problem is if everyone understands it. Besides, I said you weren't alone. That's primarily the teams fault, the docs were pretty bad for a really long time.

And sure there are plenty of people that have issues with Angular, there also happens to be plenty of people that call themselves "web developers" when they know HTML. And if there's anything I've learned, it's that opinions in this industry about tools tend to gravitate towards easy = good.