Talk:AngularJS

Reason for removing the See Also section

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 http://www.youtube.com/user/angularjs and http://www.youtube.com/watch?v=WqmeI5fZcho&list=TLJUxRYO87UWA --Mnoon (talk) 08:21, 21 July 2013 (UTC)

Need to cull the Releases list

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. 89.160.94.50 (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

Should we include a code sample/examples (as on JavaScript#Simple_examples, JQuery#Usage_styles)? I found a simple hello world on http://viralpatel.net/blogs/angularjs-introduction-hello-world-tutorial/ --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

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 which focused only on code run during $digest cycle.

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

References

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on AngularJS. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

• Attempted to fix sourcing for http://getangular.com/

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Y An editor has reviewed this edit and fixed any errors that were found.

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool. (after manually fixing Cyberbot's mistake)

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 00:13, 6 December 2015 (UTC)

"to provide structure for the journey of building an application:" - Are you kidding? What type of "journey" are we talking about here? Who in the world wrote that? Please, do not write that type of junk in a programming article, ever again. — Preceding unsigned comment added by 98.194.39.86 (talk) 04:47, 15 January 2016 (UTC)

confusion between angular1.x and 2.x+, skipping version for semver, etc

There should most likely be two different articles for the original angularJs and newer Angular platforms. There will be support for the original version for years to come, while the newer angular versions will maintain enough similarity so they could go into their own single article and most likely that's all that will be needed. There are definite naming issues here which will probably confuse newcomers. EspritsPréparés (talk) 10:05, 20 January 2017 (UTC)

suggesting a split for angular2

I'm not sure what the best terminology and strategy is, I believe there has been some confusion regarding naming preferences, so ideally only one additional page needs to be created for future angular versions EspritsPréparés (talk) 12:18, 20 January 2017 (UTC)

If this is an article on AngularJS then certainly there should be some discussion of Angular 2 and what distinguishes it. Probably it should be abbreviated and include a link to a main article on Angular2. --Larry Seltzer 18:25, 31 January 2017 (UTC)

An Angular2 article was split off a couple of weeks ago, Angular (2+) is now covered in the Angular (application platform) article. --Kjetil_r 12:11, 18 March 2017 (UTC)

Maintenance and rating of JavaScript articles

Concerning editing and maintaining JavaScript-related articles...

Collaboration...

If you are interested in collaborating on JavaScript articles or would like to see where you could help, stop by Wikipedia:WikiProject JavaScript and feel free to add your name to the participants list. Both editors and programmers are welcome.

Where to list JavaScript articles

We've found over 300 JavaScript-related articles so far. If you come across any others, please add them to that list.

User scripts

The WikiProject is also taking on the organization of the Wikipedia community's user script support pages. If you are interested in helping to organize information on the user scripts (or are curious about what we are up to), let us know!

If you have need for a user script that does not yet exist, or you have a cool idea for a user script or gadget, you can post it at Wikipedia:User scripts/Requests. And if you are a JavaScript programmer, that's a great place to find tasks if you are bored.

How to report JavaScript articles in need of attention

If you come across a JavaScript article desperately in need of editor attention, and it's beyond your ability to handle, you can add it to our list of JavaScript-related articles that need attention.

Rating JavaScript articles

At the top of the talk page of most every JavaScript-related article is a WikiProject JavaScript template where you can record the quality class and importance of the article. Doing so will help the community track the stage of completion and watch the highest priority articles more closely.

Thank you. The Transhumanist 01:06, 12 April 2017 (UTC)

Development history, erroneous sentence

This sentence speaks of 1 person and ends with "the two decided"

AngularJS was originally developed in 2009 by Miško Hevery[15] at Brat Tech LLC[16] as the software behind an online JSON storage service, that would have been priced by the megabyte, for easy-to-make applications for the enterprise. This venture was located at the web domain "GetAngular.com",[16] and had a few subscribers, before the two decided to abandon the business idea and release Angular as an open-source library.

this is either a typo or an omission and should be corrected by someone in the know.

Adam Aborns is usually credited in addition to Miško Hevery, both at Brat Tech LLC (see https://www.angularjswiki.com/angular/history-of-angularjs/ or many other references). Frequently mentioned initial team members (Google phase) are Igor Minar and Volta Jína.

Jgvictores (talk) 13:12, 25 April 2022 (UTC)