Things that suck in AngularJS

#1

Post by sbarre » Mon, Oct 28, 2013, 10:02 PM UTC

Things that suck in AngularJS
lhorie.blogspot.ca

Re: Things that suck in AngularJS

#2

Post by jacques_chester » Mon, Oct 28, 2013, 10:25 PM UTC

There's also a lot of missing fit and finish.

For example:

   watch( watchExpression, listener, [ objectEquality ] )

vs

   watchCollection( obj, listener )

Yet in watchCollection, like in watch, 'obj' can be an expression that is evaluated.

Re: Things that suck in AngularJS

#3

Post by rjaguayo » Mon, Oct 28, 2013, 10:39 PM UTC

JQuery.when is similar to $q.all http://docs.angularjs.org/api/ng.$q

Re: Things that suck in AngularJS

#4

Post by gkoberger » Mon, Oct 28, 2013, 10:46 PM UTC

Documentation is by far the worst part of Angular. I spent 90% of my time Googling and 10% writing code. (Hey, maybe that's Google's plan -- ramp up traffic to search. Synergy!)

AngularUI is confusing, mostly undocumented and often behind Angular. Splitting ngRoute/ngAnimate into their own files is an odd choice, although I assume the former is so they can replace it with the superior ui-router. Which also is weird. Like jQuery, it seems like the UI portion is just off on their own doing what they want.

Google has the chance to build the new framework that will run the web in 2-3 years. Much like Rails a few years ago. Angular is an amazing framework. It seems like they just don't care.

Angular needs someone versed in developer usability to take control of the public facing Angular stuff and give it a complete overhaul. Right now, it's the result of hundreds of people haphazardly making changes.

Re: Things that suck in AngularJS

#5

Post by psychometry » Mon, Oct 28, 2013, 10:58 PM UTC

gkoberger wrote: post #4

Documentation is by far the worst part of Angular. I spent 90% of my time Googling and 10% writing code. (Hey, maybe that's Google's plan -- ramp up traffic to search. Synergy!) AngularUI is confusing, mostly undocumented and often behind Angular. Splitting ngRoute/ngAnimate into their own files is an odd choice, although I assume the former is so they can replace it with the superior ui-router. Which also is weird.…

Is there a Javascript MVC framework that actually has good documentation, guides, and code samples? I've been working with Ember.js, but it's incredibly frustrating trying to learn a framework whose documentation is incomplete.

The other problem I've found is that docs, tutorials, and Stack Overflow posts that are even six months old are often completely useless when troubleshooting bugs in Ember.js or even learning its basic features.

It seems Angular suffers from the same complaints I have about Ember.js. Those of us who really need to just "get things done" might be better suited by a mature, well-documented framework, but does one actually exist?

Re: Things that suck in AngularJS

#6

Post by twanlass » Mon, Oct 28, 2013, 11:02 PM UTC

psychometry wrote: post #5

gkoberger wrote: post #4

Documentation is by far the worst part of Angular. I spent 90% of my time Googling and 10% writing code. (Hey, maybe that's Google's plan -- ramp up traffic to search. Synergy!) AngularUI is confusing, mostly undocumented and often behind Angular. Splitting ngRoute/ngAnimate into their own files is an odd choice, although I assume the former is so they can replace it with the superior ui-router. Which also is weird.…

Is there a Javascript MVC framework that actually has good documentation, guides, and code samples? I've been working with Ember.js, but it's incredibly frustrating trying to learn a framework whose documentation is incomplete. The other problem I've found is that docs, tutorials, and Stack Overflow posts that are even six months old are often completely useless when troubleshooting bugs in Ember.js or even learning…

I felt like Backbone.js (when I was actively using it) had really clean and complete docs. Couple that with the fact that the source is incredibly readable and debugging anything strange was never that tough.

Re: Things that suck in AngularJS

#7

Post by joshuacc » Mon, Oct 28, 2013, 11:06 PM UTC

gkoberger wrote: post #4

Documentation is by far the worst part of Angular. I spent 90% of my time Googling and 10% writing code. (Hey, maybe that's Google's plan -- ramp up traffic to search. Synergy!) AngularUI is confusing, mostly undocumented and often behind Angular. Splitting ngRoute/ngAnimate into their own files is an odd choice, although I assume the former is so they can replace it with the superior ui-router. Which also is weird.…

I agree that the documentation could be better. When I first started working with Angular I had similar issues. However, after spending a decent amount of time working with the framework, I find the documentation fairly clear. The problem is really the lack of concrete examples of how things fit together.

However, Angular UI is a totally separate set of projects that is not run by the Angular team at all. Not sure why you're giving them a hard time about it.

Re: Things that suck in AngularJS

#8

Post by adrianbg » Mon, Oct 28, 2013, 11:11 PM UTC

My biggest pet peeve is how it suppresses errors in inline expressions.

Re: Things that suck in AngularJS

#9

Post by flylib » Mon, Oct 28, 2013, 11:22 PM UTC

Surprised the knock is bad documentation (The site is awful), but I have heard that Angular has a lot better documentation then Ember currently does

Re: Things that suck in AngularJS

#10

Post by dchuk » Mon, Oct 28, 2013, 11:23 PM UTC

Shameless subreddit promotion: I (and the rest of the members) are trying to submit every single worthwhile AngularJS article to http://www.reddit.com/r/angularjs so that it becomes a solid place to keep up with AngularJS tutorials and guides.

So far we've almost doubled the subscriber-base in about 3 months so things are finally starting to snowball a bit in terms of participation.