Why does Angular.js rock? • Hacker News Board

Re: Why does Angular.js rock?

#71

Post by sahrizv » Sat, Aug 03, 2013, 7:58 PM UTC

andrewflnr wrote: post #21

sahrizv wrote: post #4

I am just starting up web development and have decided to use Django for backend. However, this Angular vs Ember comparisons have lowered my confidence as I think whatever choice "I" make, will turn out wrong in the long run. Can the experienced people here tell me what I should choose? I am fine with either style of approach to HTML(template vs declarative) and I just want a batteries included framework, which I can…

What kind of "batteries" are you looking to be included? Knockoutjs doesn't automate saving to the server (though it can do everything up to the Ajax call), and IMO it has a pretty intuitive model and near-perfect docs. As a recent convert, I would recommend that you consider it. Unless you've already rejected it for your own reasons, in which case I'm curious what those are. PS: the tutorial does have a little opaqu…

I was looking for a framework which can handle as much as possible of the configuration, plumbing and any other processes which are involved in web development. I know that is not exciting and causes limitations, but being a novice in this field, I do not want to be messing around with the basics. I rather want to focus on the core business aspects of my venture. :-)

Re: Why does Angular.js rock?

#72

Post by hayksaakian » Sat, Aug 03, 2013, 7:58 PM UTC

    It works great but what if we want the input to have the focus when the page loads? jQuery right? We grab the input and we call the focus() method in it. NO.

    With directives we want our HTML to be as self-descriptive as possible so we are going to create a focus directive.

Or you could use html5's autofocus

http://davidwalsh.name/autofocus

and cut the JS

-----

Otherwise great article, I'm really leaning hard towards angular now, over ember

Re: Why does Angular.js rock?

#73

Post by xaritas » Sat, Aug 03, 2013, 7:59 PM UTC

meowface wrote: post #65

dchuk wrote: post #55

Earlier quoted context omitted.

You can use either angular ui or angularstrap to get native angular support for bootstrap

This is kind of a dumb question, but do you know of any good solutions that allow the use of Angular with CoffeeScript, Bootstrap, AND a higher-level templating language like HAML? (I know I'm pretty much combining "hip" programming buzzwords here, but I am curious.)

I haven't used it, but I think this might be what you are looking for: https://github.com/tuyen/yeoman-angular-haml

Based on yeoman (http://yeoman.io), which I used briefly for the first time a few days ago, and it seems like a nice system. It already has pretty good integration with the AngularJS seed project.

You could probably roll something together using middleman (http://middlemanapp.com) too, with a bit more legwork.

Re: Why does Angular.js rock?

#74

Post by stevewilhelm » Sat, Aug 03, 2013, 8:21 PM UTC

> Angular has a lot of built-in services, managing $http requests, $q for promises, etc. But in this part we are not going to talk about any built-in service, because they are more complex to explain and that belongs to a new article.

Statements like this worry me. Authenticated requests to REST API's should be drop dead simple in any JS framework.

Re: Why does Angular.js rock?

#75

Post by Foxandxss » Sat, Aug 03, 2013, 8:23 PM UTC

hayksaakian wrote: post #72

It works great but what if we want the input to have the focus when the page loads? jQuery right? We grab the input and we call the focus() method in it. NO. With directives we want our HTML to be as self-descriptive as possible so we are going to create a focus directive. Or you could use html5's autofocus http://davidwalsh.name/autofocus and cut the JS ----- Otherwise great article, I'm really leaning hard towards…

True, but the directive will reach to those places where html5 is not a welcome guest.

But to be sincere, I picked one thing to a directive, there are infinite ideas but I needed one easily enough for a "hello-world" type of post.

Re: Why does Angular.js rock?

#76

Post by mcgwiz » Sat, Aug 03, 2013, 8:25 PM UTC

Certainly amusing demo.

What might actually have a chance at winning me over (having deep real-world experience with and trust of other tools) is an account of more complex usage:

- deep look at componetization/composition techniques,

- how it plays with CommonJS/AMD/Harmony,

- honest accounting of drawbacks, pain points, non-ideal usage scenarios,

- explanation of all the magic, e.g. what's happening under the covers to do data-binding, does the global namespace get polluted by DI features, etc...

Re: Why does Angular.js rock?

#77

Post by dirtyaura » Sat, Aug 03, 2013, 8:44 PM UTC

ams6110 wrote: post #25

mgkimsal wrote: post #13

Earlier quoted context omitted.

"The docs by themselves simply will not teach you how Angular works." Well said, and I agree, but I wonder why this is? There's some cred to be gained by making and using something so impenetrable that only a select handful of people 'just know' how something works, and everyone aspires to be like them? I've found plenty of people/blogs/sites telling me I'm doing angular 'wrong' (and not just angular - other framewor…

What these "younger devs" don't realize is that in most cases they are simply reinventing stuff that has existed for years. Even today, the best JS MVC frameworks only just provide the capabilities to build UIs that (for example) were trivial in PowerBuilder 20 years ago. The fact that it's considered "gee whiz" that you can enter a value into a form field and have that value automatically validated and bound to an a…

I wouldn't say that Angular is reinventing the wheel. Elegant and efficient two-way data binding is a non-trivial problem, and I haven't seen it implemented well (or at all!) in any UI framework that I have worked with in the last 15 years.

Re: Why does Angular.js rock?

#78

Post by anton-107 » Sat, Aug 03, 2013, 9:00 PM UTC

meowface wrote: post #65

dchuk wrote: post #55

Earlier quoted context omitted.

You can use either angular ui or angularstrap to get native angular support for bootstrap

This is kind of a dumb question, but do you know of any good solutions that allow the use of Angular with CoffeeScript, Bootstrap, AND a higher-level templating language like HAML? (I know I'm pretty much combining "hip" programming buzzwords here, but I am curious.)

Angular + Bootstrap = use Angular UI Bootstrap. For Coffee use on-the-fly transcompilation of your choice (i.e. grunt-contrib-coffee + grunt-contrib-watch). For any of higher-level templating again use on-the-fly compilation (i.e. grunt-haml + grunt-contrib-watch)

Re: Why does Angular.js rock?

#79

Post by Foxandxss » Sat, Aug 03, 2013, 9:10 PM UTC

stevewilhelm wrote: post #74

> Angular has a lot of built-in services, managing $http requests, $q for promises, etc. But in this part we are not going to talk about any built-in service, because they are more complex to explain and that belongs to a new article. Statements like this worry me. Authenticated requests to REST API's should be drop dead simple in any JS framework.

Well, not that complex, I just tried to show the minimum things possible. My first idea for a service was a twitter search but that implies an explanation of $http and things related with it. Auth request are not that bad, it is certainly not as simple as we want (but that happen in every client side framework) but not bad. I want to cover auth in a future article.

Re: Why does Angular.js rock?

#80

Post by piranha » Sat, Aug 03, 2013, 9:12 PM UTC

bsaul wrote: post #41

caioariede wrote: post #17

What are the alternatives to Angular.js that does not use this Dependency Injection magic?

Dependency Injection can really be done in a dark magic way (the java / spring way), but after reading the source code, i can tell you angular.js way of doing it is really not that dark. More importantly, is extremely easy to use. No .xml file, no configuration file, just put the service in that function signature, done (unless you want to minifiy, which means you'll also have to add it as a string right next to it).

Well, in my option DI is one of the worst parts of Angular. It's a module system which can't be integrated with anything. Doing something like commonjs/amd would be much nicer:

app.controller('Name', function(require) { var $scope = require('$scope'); var y = require('some-service'); });

And suddenly, no problems and no weird syntax!