> This is possible, I haven't used Aurelia to comment. I took a brief look at the documentation. It appears as though it's a "batteries included" framework fav

> This is possible, I haven't used Aurelia to comment. I took a brief look at the documentation. It appears as though it's a "batteries included" framework favoring convention over configuration, with a custom templating specification a la AngularJS. The nice thing about React - to me - is the straightforward mapping of Javascript control flow to DOM. You don't have to learn a custom templating protocol in order to render things and it's ridiculously easy to create encapsulated components. data.map((el) => <div>{el}</div>) var Foo = React.createClass({render: () => ...}); Gets you <Foo/> Even less syntax noise if you take advantage of stateless functional components. [0] Compare this to Angular's ridiculous directive declaration syntax nightmare... cringe :) Aurelia isn't that much better in this regard [1] There's a bunch of boilerplate that needs to be introduced for you to create simple custom elements: lots of .bind, <require> tags, separate files for each custom element. Bleh :) Maybe it's better when you're working with a bunch of developers with bad habits, or have to grok a huge code base. There, I can see some of its conventions and structure coming in handy. Still, I don't see why OP is throwing a hissy fit over it. Everyone has their favorite tools ¯\_(ツ)_/¯ 0. https://facebook.github.io/react/docs/reusable-components.html#stateless-functions https://facebook.github.io/react/docs/reusable-components.ht... 1. http://aurelia.io/hub.html#/doc/article/aurelia/templating/latest/templating-custom-elements/4 http://aurelia.io/hub.html#/doc/article/aurelia/templating/l...