4 ms·

> It's one of the first web framework that comes with a specific testing framework. Where on earth did you get that idea? > AngularJS didn't became popular be

> It's one of the first web framework that comes with a specific testing framework. Where on earth did you get that idea? > AngularJS didn't became popular because it was from Google But it was definitely helped that it was so heavily promoted by Google > your point about ng-model and scopes is valid. But it's not a angular problem, it's a javascript issue Again...what? JavaScript doesn't have `ng-model`...Angular does. It's an Angular problem through and through.

aikah 12y ago
> Where on earth did you get that idea? Well you didn't disprove my assertion (I was obviously talking about front end frameworks) by citing a front end framework that came with an extensive testing framework. So why on earth are you saying something without backing it with facts? > But it was definitely helped that it was so heavily promoted by Google I started using AngularJS in 2011 it had 0 promotion from Google. It wasn't even a Google product at that time. > Again...what? JavaScript doesn't have `ng-model`...Angular does. It's an Angular problem through and through. No the problem is that Javascript doesn't have pointer variables,therefore when using variables in a scope you need to use object properties and not objects directly if you want to refer to it in the outer scope. It has nothing to do with angular but everything to do with the way Javascript works.
- ralfn 12y ago
  >Well you didn't disprove my assertion (I was obviously talking about front end frameworks) by citing a front end framework that came with an extensive testing framework. So why on earth are you saying something without backing it with facts? Let me help settle which of you two is the liar then. Ember comes with tooling for unit-tests and so does Qooxdoo (which also includes Selinium support out of the box). And that's just two of three i'm familiar with. >No the problem is that Javascript doesn't have pointer variables There you go: pass-by-reference semantics (i.e. pointer variable) var flow = function( init ){ return function( v ){ if( v !== undefined ) init = v; return init; } } > It has nothing to do with angular but everything to do with the way Javascript works. No, it has to do with the ad-hoc programming language shoehorned into dom-nodes. Javascript has lexical scoping, Angular does not, because its control-flow lives in your dom. It also doesn't have encapsulation or proper step-debugging this way. But none of that has anything to do with Javascript. If all that logic lived in a .js file lexical scoping would be possible and recommended.

aikah 12y ago

> Where on earth did you get that idea? Well you didn't disprove my assertion (I was obviously talking about front end frameworks) by citing a front end framework that came with an extensive testing framework. So why on earth are you saying something without backing it with facts? > But it was definitely helped that it was so heavily promoted by Google I started using AngularJS in 2011 it had 0 promotion from Google. It wasn't even a Google product at that time. > Again...what? JavaScript doesn't have `ng-model`...Angular does. It's an Angular problem through and through. No the problem is that Javascript doesn't have pointer variables,therefore when using variables in a scope you need to use object properties and not objects directly if you want to refer to it in the outer scope. It has nothing to do with angular but everything to do with the way Javascript works.

ralfn 12y ago
>Well you didn't disprove my assertion (I was obviously talking about front end frameworks) by citing a front end framework that came with an extensive testing framework. So why on earth are you saying something without backing it with facts? Let me help settle which of you two is the liar then. Ember comes with tooling for unit-tests and so does Qooxdoo (which also includes Selinium support out of the box). And that's just two of three i'm familiar with. >No the problem is that Javascript doesn't have pointer variables There you go: pass-by-reference semantics (i.e. pointer variable) var flow = function( init ){ return function( v ){ if( v !== undefined ) init = v; return init; } } > It has nothing to do with angular but everything to do with the way Javascript works. No, it has to do with the ad-hoc programming language shoehorned into dom-nodes. Javascript has lexical scoping, Angular does not, because its control-flow lives in your dom. It also doesn't have encapsulation or proper step-debugging this way. But none of that has anything to do with Javascript. If all that logic lived in a .js file lexical scoping would be possible and recommended.