Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Things that suck in AngularJS

lhorie.blogspot.ca

Post reply on HN
Print view View original

121–130 of 151 posts

Re: Things that suck in AngularJS

#121

Post by pavlov »

jowiar wrote: post #54

Angular, when it feels right, makes me incredibly productive, but I feel like I spend 90% of my time banging my head against a brick wall. One of the single biggest usability features of anything is giving things appropriate names. The "other half" of Karlton's law is well in effect here. Angular fails miserably at this task. And that makes reading documentation, as well as maintaining enough context in my head to be…

I feel like I spend 90% of my time banging my head against a brick wall.

Why do people want to work with a technology like that?

Personally I feel that the worst part of programming is when you're stuck trying to decipher the inner workings of an intermediate layer. It's so frustrating and futile, and I'm not learning anything generally useful because mastering arcane workarounds for technology layer X doesn't translate to anything else.

I'll much rather work with technology that doesn't make me feel magically productive 10% of the time, but does make me actually productive 99% of the time. There are plenty of those around.

Re: Things that suck in AngularJS

#122

Post by Narretz »

arbus wrote: post #83

> The page for directives is another (in)famous part of the docs that, despite relating to one of the most important aspects of the framework, is often derided as being overly dry While that used to be true, the directives page recently got updated to provide a much better and simple guide to directives along with plently of code samples - http://docs.angularjs.org/guide/directive

There is still some work to do. Read the paragraph about transclude : true? $transclude is one of the best features of advanced directives, and the paragraph is still the old one which leaves you with a "... what?" even after you read it 5 times. An example is very much in roder here, but how long should the article be? Before, this section was actually in the guide, and the doc for $compile was neat and clear. Now it's actually messier than before.

Re: Things that suck in AngularJS

#123

Post by atulagarwal »

AngularJS explicitly [1] states that its suited best for standard CRUD apps. If you need to do something which requires touching the DOM or some low level manipulation, better stay off it. We decided against it while building our GUI Editor ( adpushup.com), and decided on Backbone (w/ Backbone relational). Backbone is a library (as opposed to being a framework) and plays really nice with jQuery and vanilla JS.

However, there'll be projects/components for which AngularJS (or EmberJS) would be better suited, and we'll surely love to give it a try.

[1] : http://docs.angularjs.org/guide/overview

Re: Things that suck in AngularJS

#124

Post by taude »

novaleaf wrote: post #91
pygy_ wrote: post #67

Earlier quoted context omitted.

[0] which leads to [1] Notice the "Copyright 2009 - Angular / BRAT Tech. LLC" at the bottom of the page. IIRC, They had a plan to provide a paid or freemium server-side counterpart. edit: freemium, see the first revision of getangular.com[2], there's a pricing tab which disappeared later on. update 2 : they were not acquired, they abandoned the startup because it did not get enough traction. The framework lived on, t…

i don't dispute this, but it pretty much flies in the face of everything the team has publicly communicated so far. Any thoughts on why the whitewash? Maybe to get better traction as being a 100% google skunkwork?

Easier, simpler story to tell than the long version, of which the details don't really matter?

Re: Things that suck in AngularJS

#125

Post by kosinus »

collyw wrote: post #110
kosinus wrote: post #27

Earlier quoted context omitted.

If you're really spending 90% on Google, and 10% writing code, then you're doing it wrong. At least a good 30% of your time should involve reading code. In any framework. That said, AngularJS' code is magic in places. The magic is contained within small modules, or at least as small as those can get for what they're supposed to do. But documentation is only enough to get you started. In any framework. (And in my expe…

Why? I use Django on the server side, the documentation is superb (compared to Angular's). I hardly ever need to dig inside the code, unless I want to do something quite special. I have a good idea of how the framework works, what pieces fit together where, but I never feel the need to go in and read the code for it. And what about proprietary software? I am sure there are plenty of frameworks where you can't get to…

Between frameworks like Ruby on Rails, Node.js, AngularJS and smaller libraries like Backbone.js, jQuery, and jQuery UI, I've relied more on code for all of them. Documentation has only ever helped me to get started, and as a quick reference. But do anything significant, and thorough understanding is simply a must; something I can only find in code.

I also do a good amount of work with the Twitter and Facebook APIs, and in my spare time work on a fairly complex Cocoa project. Working with all of these is a whole lot of poking at interfaces until they do what I want. These all have tons of documentation, but they'll never be pleasant for me to work with.

Re: Things that suck in AngularJS

#126

Post by shaydoc »

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…

KnockoutJS.com is by far the best in terms of documentation and usability for novices.

Re: Things that suck in AngularJS

#127

Post by ds_ »

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

The docs are fine. There can always be improvements, but it isn't orders of magnitude worse than other frameworks as people persistently claim.

Re: Things that suck in AngularJS

#128

Post by bpicolo »

bearwithclaws wrote: post #77

Been using (or, trying to use) AngularJS for the past 2 months. The way to get around the bad documentation for me are sites like http://egghead.io/ and http://thinkster.io/ (and of course, tons of SO-ing).

Egghead is great and all, but it's really useless if I want some important feature explained in-depth. (What do I need to define for it, what actions does it have, what is it use for, what is the best structure for it, etc etc)

Re: Things that suck in AngularJS

#129

Post by jwblackwell »

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

The doc for "mock" is a funny example of how poor the docs are in places http://docs.angularjs.org/api/angular.mock

Re: Things that suck in AngularJS

#130

Post by optymizer »

RossM wrote: post #113

I've been turned off by the Angular docs (feels like how I found API refs intimidating when I started coding) - can anyone recommend an alternative or book?

I've read "Mastering Web Application Development with AngularJS" and I thought it was pretty good at explaining difficult concepts in AngularJS.
Post reply on HN