return <ul>
{this.props.items.map(item => <li>{item}</li>)}
</ul>;
vs. the Angular version: <ul ng-repeat="item in items">
<li>{{ item }}</li>
</ul>
The Angular template is more readable at the expense of ngRepeat's complexity. Neither example includes Component/directive boilerplate. The directive boilerplate is generally worse, because it requires a separate template file or an ugly template string, knowledge of the directives API itself which is baroque in the extreme, and $scope-wrestling (whereas JSX' scope is the same as JS').In my opinion reuse of the React component is more straightforward, you explicitly import/require it while in Angular you specify its providing module as an angular.module dependency, which has implications for config block ordering.
In React, I just create a renderNode method that's called by render at the top level, and renderNode on non-terminal nodes returns <div>{children}</div> where children is a map whose mapping function returns this.renderNode. The entire algorithm is grokkable at a single glance, and there's no need to create Directives to add any fancy features or special cases in the future. No need to read pages of documentation about ng-repeat and its intricacies; it's all just Javascript.
Yes, Angular "just works." But React "just works" the first time you try it.
<ul>{props/items/item/<li>{.}</li>}</ul>
But not interactiveAlso the angular equivalent would be
<ul><li ng-repeat="item in items">{{item}}</li></ul>
And the react-templates equivalent would be <ul><li rt-repeat="item in this.state.items">{item}</li></ul>
[1] http://wix.github.io/react-templates/