AngularJS 1.3.0

I don't like Angular. Everybody likes it but I don't.

It feels like 2004 all over again. SOAP! SOAP! XML! GWT! ColdFusion!!!!1onene!!!1

I also don't like working with Google toolchain, because for a company full of smartest dudes on the planet it certainly seems like these dudes don't care about their customers.

Below is a list of reasons why I dislike Angular.

1. GAE documentation sucks, GoLang documentation sucks and indeed Angular documentation sucks.

2. By using Angular you are throwing away the toolchain we have been honing and making better for the last fifteen years.

3. Debugging - If I have learned anything from the XML dark ages it is that you do not want to program in a language that is not debuggable. And yet, here comes Google and does it again!

4. Overloading semantics. I hate Angular for just going and reinventing so many of the words and context we use in this trade.

5. Angular is not free! I would not use Angular for the same reason I would not use Java. I would hate to tie my future to this uber monstrous corporation's whims.

Thinking about Angular I realized (yet again!) that Google has jumped the shark. It is no longer pragmatic and cheeky startup of fifteen years ago. Nowadays it is more akin IBM and Microsoft of old.

Edit: Basically to me Angular is another stab at the softcoding - where Angular is the app and your code is softcoded definitions of behaviors. And as such it will eventually fail for the same reasons all the similar projects have done so before. Some of which are listed above.

Check out https://github.com/spoike/refluxjs better explained and more elegant implemented( no string dirty-checking for one).

You can use it anywhere but it'll be especially helpful for long lists. Angular binds anything in double curlies, creating watchers that dirty check and evaluate with every digest cycle. It's tempting (and IMO Angular incorrectly encourages users) to use double curlies for templating everwhere, so in typical list views you can end up with thousands of watchers on data that never needs to change once the page is rendered. This is slow, especially for searching and sorting. Further reading[1]

Before this release it's been necessary to write custom directives or use a tool like Bindonce[2] to turn off data binding where it's not needed.

[1] http://tech.small-improvements.com/2013/09/10/angularjs-perf...

[2] https://github.com/Pasvaz/bindonce

Err..

1. I admit Angular documentation sucks, but that's not atypical in any open source. It's getting way better btw, and there are tons of resources from 3rd party.

2. Which toolchain are you referring to? If we're talking Web/JavaScript (where Angular is for), I can say the toolchain e.g. Grunt is quite recent.

3. I somewhat agree with this. We can use e.g. Chrome Dev tools and Batarang (Angular Chrome plugin), but definitely there's room for improvements.

5. Care to elaborate your definition of free? Even for Java, I can say a significant ecosystem for Java is open source. Sure, some Enterprise prefer Java Enterprise Edition, but many are satisfied with Spring and other open source Java-based solutions.

The´re a bit different. Actaully the AngularDart has features that 1.3 don't have, like the new router, and I'm sure there is something in 1.3 that don't exist in AngularDart. But AngularDart seems to be the more "advanced" one.