HTML itself is declarative in nature. All frameworks should embrace this.
By looking at React docs, I can tell you from my experience that it'll be pain in the s to maintain a large scale React application.
AngularJs' declarative way gives an app maintainability and highly test-ability. These two things are not the luxury but a must have requirement for any large scale long-live application.
http://www.youtube.com/watch?v=x7cQ3mrcKaY&list=FLuFwYXJkbMi...
Of course you're free to agree or disagree with their argument, but I wouldn't assume they are just newbs who are unaware of standard best practices. They know the "rules" and are breaking them consciously.
2) React programs tend to be very "dearative" in my eyes. Any declarative language still needs abstraction facilities: ie functions.
3) you can trivially implement any "more declarative" model you want on top of React's stellar core.
4) all of the benefits of test ability from angular apply to react too
Sorry about typos, on phone
This is what you typically get at the end in an Angular app. You don't need to "figure out" things where they are and what they are, and what they do in DOM.
Show me this declarative thing in React.
And this is just one part of Angular.
That said, I've found react to be very declarative, especially over the raw jQuery and Backbone I'd used before. Most of the components I write have no state, and render() declares how to render them from any state, without having to worry about how to change things on state changes.
<tabManager background={'blue'}> <tab closeButton={true}> Hello {this.props.Name} </tab> </tabManager>
Would be valid in react.
Check out http://facebook.github.io/react/#todoExample, specifically the render function.
I think this is pretty easy to understand:
<div>
<h3>TODO</h3>
<TodoList items={this.state.items} />
<form onSubmit={this.handleSubmit}>
<input onChange={this.onChange} value={this.state.text} />
<button>{'Add #' + (this.state.items.length + 1)}</button>
</form>
</div>And if you don't like html in js, you could always embed ClojureScript in ClojureScript :-):