aurelia

This is the stuff that is handled by angular or ember or knockout or aurelia or etc.

I have also been loving React.js + Flux, but Aurelia more so than React these days.

If the Aurelia docs suggest using Jasmine to test the application, especially if they help setting up html fixtures and data, then that's encouraging.

Before Aurelia adopted Zenhub, I had never heard of them before to be honest.

This guy says he is thinking of using Aurelia instead.

I've been using Aurelia a bit here and there and like it a lot.

One of the APIs we don't use...but we will allow you to export your Aurelia elements to a document.register form for v1.

So, before we hit v1 you will be able to do that and then take an Aurelia Web Component into a non-Aurelia app and use it, the same way you would use a Polymer element.

I'll probably end up moving to Aurelia (or something like it) because it's so pluggable and you can use it with React or not.

See Aurelia or Este.js or even web components.

Can someone from the Aurelia team clarify this?

For now it's all DIY so, if I join your Aurelia team, I have to spend a bunch of time learning how your testing works?

As a side note, Aurelia will be able to "export" its custom elements to Web Components.

I think Aurelia's rigid, opinionated structure is clearer and succinct than Angular's more "framework" approach.

> "a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc" Part of the problem with the Javascript ecosystem is that you have to use so many different tools/libraries to create a "simple" app.

Comparing jquery to React (or Angular/Aurelia/etc) is obvious but the article is great for beginners though.

I have actually been building a production application in Rob's newer framework and Durandal successor: Aurelia.

Aurelia looks interesting to me, but I don't think it uses React by default.