aura

A scalable, event-driven JavaScript architecture for developing component-based applications.

Web Development

Explore on GitHub Read Hacker News discussions

2Distinct people

3Mentions

0Explicit recommenders

2.9KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A scalable, event-driven JavaScript architecture for developing component-based applications.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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, 3:56:07 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 week3 dated mentions

Observed mentions: 2013-01-26 18:41:04 UTC to 2013-05-11 15:15:18 UTC. Weeks start Monday, UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Jan 21	2013-01-21 00:00:00 UTC	2013-01-28 00:00:00 UTC	1	1
Jan 28	2013-01-28 00:00:00 UTC	2013-02-04 00:00:00 UTC	0	0
Feb 4	2013-02-04 00:00:00 UTC	2013-02-11 00:00:00 UTC	0	0
Feb 11	2013-02-11 00:00:00 UTC	2013-02-18 00:00:00 UTC	0	0
Feb 18	2013-02-18 00:00:00 UTC	2013-02-25 00:00:00 UTC	0	0
Feb 25	2013-02-25 00:00:00 UTC	2013-03-04 00:00:00 UTC	0	0
Mar 4	2013-03-04 00:00:00 UTC	2013-03-11 00:00:00 UTC	0	0
Mar 11	2013-03-11 00:00:00 UTC	2013-03-18 00:00:00 UTC	0	0
Mar 18	2013-03-18 00:00:00 UTC	2013-03-25 00:00:00 UTC	1	1
Mar 25	2013-03-25 00:00:00 UTC	2013-04-01 00:00:00 UTC	0	0
Apr 1	2013-04-01 00:00:00 UTC	2013-04-08 00:00:00 UTC	0	0
Apr 8	2013-04-08 00:00:00 UTC	2013-04-15 00:00:00 UTC	0	0
Apr 15	2013-04-15 00:00:00 UTC	2013-04-22 00:00:00 UTC	0	0
Apr 22	2013-04-22 00:00:00 UTC	2013-04-29 00:00:00 UTC	0	0
Apr 29	2013-04-29 00:00:00 UTC	2013-05-06 00:00:00 UTC	0	0
May 6	2013-05-06 00:00:00 UTC	2013-05-13 00:00:00 UTC	1	1

What Hacker News says

3 sources

romain_dardour·May 11, 2013

You should take a look at aura.js (http://github.com/aurajs/aura). Abstracts many of the steps of this article (require.js, bower...) and offers a decoupled architecture for scalable and well structured apps. There's also a yeoman generator, and they have an extensions system that seamlessly integrate handlebars.js for example.

In Building HTML5 Apps with Yeoman and Backbone

romain_dardour·Mar 21, 2013

While I agree about the "no reinventing the wheel" part (after all that's one of the benefits of our product), I think Cappucino had made some choices that the random developer could not come to terms with. I don't think that this is due to laziness or rouded-corner cravings (although the "new shiny toy" effect is very much existing). I think this has more to do with the different timelines web developers face when building apps. Not all of them can afford the long learning curves required by Cappucino and the fact that objective-J is only useful for Cappuccino. Not all of them need to build app-looking apps or spend lots of time bending the defaults to look like something else So the web community turns to low learning curve libraries as a side effect of not having the time to commit (as opposed to not wanting), better ones coming out al

Read the rest

l the time (things moving at a whole order of magnitude faster than in other software development areas), and using only 10% of the power brought by cappuccino. This encourages more quick, single feature libs, which in turns brings more developers into that worldview. Note that this argument is not about wether this is right or wrong. More about the why. One can note that making those micro libraries work together is getting harder and harder, and that some folks (full disclaimer, we are one of those) are building glue layers and light architectures to guide developers and ease integration and make those libraries interact together seamlessly. Take http://github.com/aurajs/aura (that's the one we're working on). It acknowledges both the fact that small, single-feature libraries are the way the web is heading, and that making those interoperable, and easy to load (a clean module system is central to aura) needs work. Maybe small, badly written, non interoperable, single use libraries are just a step on the way to a truly modular, flexible and light web development process.

In I’m done with the web

politician·Jan 26, 2013

I've also successfully implemented Zakas' [1] approach after watching his presentation "Scalable Javascript Application Architecture" [2] and abandoning Backbone.Aura [3]. Aura theoretically implements this, but in practice we found that it made some assumptions that were incompatible with our needs. Consequently, we rolled our own implementation. [1] http://www.nczonline.net/blog/about/ [2] http://www.youtube.com/watch?v=vXjVFPosQHw [3] https://github.com/aurajs/aura

In A new development era