From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Free Software / Software / Computing  (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Free Software, a collaborative effort to improve the coverage of free software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Software.
Taskforce icon
This article is supported by WikiProject Computing (marked as Low-importance).

Reason for removing the See Also section[edit]

I've just removed the See Also section from this article. It linked to Backbone, Ember and Meteor, but as usual with such sections it didn't explain the criteria for inclusion/exclusion. I know these decisions are difficult to pin down without expressing any bias (why Backbone if not Knockout? why Meteor if not Firebase? what is a library vs a framework vs a full stack?) so I suggest we leave this section empty until there is a satisfactory Comparison of Javascript MV* Frameworks article to which we can link. Any objections? - Pointillist (talk) 00:13, 1 June 2013 (UTC)

Attempting to add the following: Directives - Teach the browser new tricks. Someone said that HTML 6 goes under the name of Angular b/c of HTML 6 which may explain just how powerful AngularJS's framework is perceived. Three phases of the bootstrapper.

  1. Wait for the DOM to load
  2. Create a new Injector
  3. Compile Service is like compiling in C or C++. It walks the DOM and locates all the directives like "ng-app".
  4. Link Phase - The link phase attaches all the directives to scope.

Cite: Writing Directives - Author Unknown link on world wide web and --Mnoon (talk) 08:21, 21 July 2013 (UTC)

Need to cull the Releases list[edit]

The Releases list fails WP:NOTCHANGELOG, I'm afraid:

Changelogs, release histories or release notes. An article about a product may include a prose history of its development and major improvements. Tables or lists of changes should be avoided; instead, significant changes should be merged into – and contextualised in – the product's history. Note that, in addition to being unencyclopedic, lists of changes and releases are also unsuitable for inclusion in Wikipedia articles as they're usually drawn – often verbatim – from primary sources.

I image we'll end up with a short list of major releases, with the key differences summarised. We'll need reliable third party sources for those. Any idea who has covered this who isn't a Google employee or contributor to AngularJS? - Pointillist (talk) 18:54, 19 September 2013 (UTC)

So... it's been three months. Does nobody object if I simply delete the entire Releases list section? - Pointillist (talk) 14:41, 23 December 2013 (UTC)
As a random passer-by I object because of the awesomeness of the codenames. One does not simply delete awesomeness. (talk) 15:47, 8 January 2014 (UTC)
As another passer-by I do not object. Please go ahead. Having pages over pages of irrelevant dates and version numbers is not helpful. I came here to get an idea how angularJS evolved and how relevant it was in its early years but instead I'm confronted with this monster list of nothing? - Giszmo (talk) 19:09, 9 December 2014 (UTC)

Code sample[edit]

Should we include a code sample/examples (as on JavaScript#Simple_examples, JQuery#Usage_styles)? I found a simple hello world on --Aprillion 18:27, 16 April 2014 (UTC)

Go ahead but I find it does AngularJS no justice to not show controllers. It's an MVC framework and showing only a V with a bit of M is meh. --Giszmo (talk) 19:14, 9 December 2014 (UTC)

I reverted the addition of a new section on performance monitoring[edit]

Addition diff, removal diff. Concern was: partly out of scope, applying to other frameworks and JS generally, and partly promotional. Reproduced below:

Traditionally, javascript applications performance measured by time required to fetch html page and all linked resources from the server till the moment application initialize. Good example of such monitoring would be service provided by New Relic company. New Relic Browser service keep track of page load time, onload events, as well as tracking timing of AJAX requests made by javascript application.
Company SOASTA provides service mPulse specifically designed for performance monitoring of single-page application's. Monitoring is done via small javascript module loaded on the page, which intercepts events fired by AngularJS, Backbone.js, Ember.js and other frameworks.
AngularJS distinct feature is $digest cycle. $digest cycle does dirty checking of data in the scope, as well as making all necessary changes and react to all emitted events. Common problem with that is complex code running synchronously as part of $digest loop. Since browsers run javascript in the single thread, any synchronous long running code potentially might cause animation slowdowns and, sometimes, completely lock browser. To address this Angular-specific issue, company Meaningful Randomness created service ngMetrics[1] which focused only on code run during $digest cycle.

Bold formatting as originally submitted by contributor. Comments? Samsara 21:05, 31 August 2015 (UTC)

  1. ^ "ngMetrics - Performance Metrics For Serious Angular Applications".