HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
angular-ui
community
OPEN SOURCE2013–2013
angular-ui / community · Archived

community

Placeholder repo for discussion

Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
1Explicit recommenders
23GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Placeholder repo for discussion

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

We're using AngularJS for the second time on a project, and it's great. While I found the basics easy to pick up, some of my team struggled a bit more (but they've also spent…

Ycros used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day2 dated mentions

Observed mentions: 2013-09-03 00:20:55 UTC to 2013-09-26 22:57:37 UTC.

012013-09-03 00:00:00 UTC to 2013-09-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 32013-09-04 00:00:00 UTC to 2013-09-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-05 00:00:00 UTC to 2013-09-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-06 00:00:00 UTC to 2013-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-07 00:00:00 UTC to 2013-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-08 00:00:00 UTC to 2013-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-09 00:00:00 UTC to 2013-09-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-10 00:00:00 UTC to 2013-09-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-11 00:00:00 UTC to 2013-09-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-12 00:00:00 UTC to 2013-09-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-13 00:00:00 UTC to 2013-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-14 00:00:00 UTC to 2013-09-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 142013-09-15 00:00:00 UTC to 2013-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-16 00:00:00 UTC to 2013-09-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-17 00:00:00 UTC to 2013-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-18 00:00:00 UTC to 2013-09-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-19 00:00:00 UTC to 2013-09-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-20 00:00:00 UTC to 2013-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-21 00:00:00 UTC to 2013-09-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-22 00:00:00 UTC to 2013-09-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-23 00:00:00 UTC to 2013-09-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-24 00:00:00 UTC to 2013-09-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-25 00:00:00 UTC to 2013-09-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-26 00:00:00 UTC to 2013-09-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 26

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 32013-09-03 00:00:00 UTC2013-09-04 00:00:00 UTC101
Sep 42013-09-04 00:00:00 UTC2013-09-05 00:00:00 UTC000
Sep 52013-09-05 00:00:00 UTC2013-09-06 00:00:00 UTC000
Sep 62013-09-06 00:00:00 UTC2013-09-07 00:00:00 UTC000
Sep 72013-09-07 00:00:00 UTC2013-09-08 00:00:00 UTC000
Sep 82013-09-08 00:00:00 UTC2013-09-09 00:00:00 UTC000
Sep 92013-09-09 00:00:00 UTC2013-09-10 00:00:00 UTC000
Sep 102013-09-10 00:00:00 UTC2013-09-11 00:00:00 UTC000
Sep 112013-09-11 00:00:00 UTC2013-09-12 00:00:00 UTC000
Sep 122013-09-12 00:00:00 UTC2013-09-13 00:00:00 UTC000
Sep 132013-09-13 00:00:00 UTC2013-09-14 00:00:00 UTC000
Sep 142013-09-14 00:00:00 UTC2013-09-15 00:00:00 UTC000
Sep 152013-09-15 00:00:00 UTC2013-09-16 00:00:00 UTC000
Sep 162013-09-16 00:00:00 UTC2013-09-17 00:00:00 UTC000
Sep 172013-09-17 00:00:00 UTC2013-09-18 00:00:00 UTC000
Sep 182013-09-18 00:00:00 UTC2013-09-19 00:00:00 UTC000
Sep 192013-09-19 00:00:00 UTC2013-09-20 00:00:00 UTC000
Sep 202013-09-20 00:00:00 UTC2013-09-21 00:00:00 UTC000
Sep 212013-09-21 00:00:00 UTC2013-09-22 00:00:00 UTC000
Sep 222013-09-22 00:00:00 UTC2013-09-23 00:00:00 UTC000
Sep 232013-09-23 00:00:00 UTC2013-09-24 00:00:00 UTC000
Sep 242013-09-24 00:00:00 UTC2013-09-25 00:00:00 UTC000
Sep 252013-09-25 00:00:00 UTC2013-09-26 00:00:00 UTC000
Sep 262013-09-26 00:00:00 UTC2013-09-27 00:00:00 UTC101

What Hacker News says

2 sources
Ycros·Sep 26, 2013Recommendation phrase
We're using AngularJS for the second time on a project, and it's great. While I found the basics easy to pick up, some of my team struggled a bit more (but they've also spent less time doing heavy client-side JS development). The biggest problem AngularJS has is documentation. Some of it is missing, some of it is poorly explained, all of it should have examples. The developer guide and API reference both need a rework/rewrite. I think the team should focus on this after this major 1.2 release. What comes out of poor documentation is that best practices are not immediately obvious, because if you're trying to guess things from just the API and just picking a random way to achieve your end result, chances are you're going to do it wrong. This has been identified at https://github.com/angular-ui/community/issues/1 so hopefully it's going to
Read the rest
get better. The major thing which I think almost everyone gets wrong at first are the relationships between templates, scopes, controllers, services and your actual data. If you get this wrong you'll either end up writing a bunch of tricky workaround code, having memory leaks or subtle data binding bugs. I highly recommend everyone watches the best practices video from the AngularJS team at http://www.youtube.com/watch?v=ZhfUv0spHCY
In AngularJS is amazing, and hard as hell

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.