News for hackers. Stuff that matters.
Re:AngularJS: Factory vs. Service vs. Provider by camus2 on Sunday May 04, 2014 @09:51PM (#7696651)
a lot of people put html strings into directives so it has nothing to do with angular. Furthermore , in angular the HTML looks like a template, not just html ,with expressions , ng- everywhere ...

I dont care about this but let's just not pretend Angular solves the HTML template in code issue . It's far from inobstrusive.

Re:AngularJS: Factory vs. Service vs. Provider by zoomerang on Sunday May 04, 2014 @10:17PM (#7696706)
You can cheat in any framework. The difference is that angular strongly encourages you towards one design, whereas React.js does not. (Directives are also not part of your normal daily workflow. Many projects wouldn't even use them).

Yes, angular templates are templates, not pure HTML. That's the idea. I'm not sure what your point is there.

Re:AngularJS: Factory vs. Service vs. Provider by mikewhy on Sunday May 04, 2014 @10:37PM (#7696747)
> I cannot stand codebases that mix code and markup together.

In Angular people can write

    app.directive('myDirective', function () {
      template: "<strong>oh no</strong>"
    });
which is what I think they were getting at.
Re:AngularJS: Factory vs. Service vs. Provider by zoomerang on Monday May 05, 2014 @12:11AM (#7696901)
Sure, but that's not idiomatic Angular. I'd wager the majority of Angular projects don't even use custom directives.
Re:AngularJS: Factory vs. Service vs. Provider by camus2 on Sunday May 04, 2014 @11:45PM (#7696857)
in React templates are not pure html either,I dont get your point.