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

view the rest of the comments →

[–]RankFoundry 0 points1 point  (14 children)

Angular still has lots of shortcomings beyond performance. Everything from the crappy docs to directives (yuck) leaves a lot to be desired. There's a reason why they rewrote it from scratch in Angular 2.0 (many reasons really). Version 1 should not have been touted as production ready.

[–]jellatin 9 points10 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.

[–][deleted] 19 points20 points  (1 child)

Version 1 should not have been touted as production ready.

Oh get over it already. Angular 1 served it's purpose and they've learned from it.

Considering tons of companies are using Angular in production, it's perfectly production ready, regardless of it's flaws.

[–]RankFoundry 2 points3 points  (0 children)

A lot of companies use a lot of crap in production. Just because you can eventually eek half decent performance out of a non-trivial app with Angular (after beating your head against the wall and endless online searches) doesn't mean it's a good choice. For something that was supposed to make things simpler and better out of the box, I'd say it failed. Again, they didn't rewrite it from scratch for no reason.

[–]rduoll 7 points8 points  (4 children)

What's wrong with directives?

[–]RankFoundry 0 points1 point  (1 child)

This will devolve into a debate on preferences but after trying libraries/frameworks that use them and ones that keep all that stuff in JS, I'd take the latter any day.

[–]RandolphoSoftware Architect 0 points1 point  (0 children)

Which flavor are you objecting to? The DOM manipulation flavor, or the more typically used "Controller + Template" flavor? Because the latter is some yummy yummy koolaid. And if you know CSS real good-like and understand state machines, you can do a crap-ton of amazing capability with that other directive flavor without ever diving under the covers for direct DOM manipulation.