5 ms·

React v0.8 is out

96 points by zpao 13y ago

spicyj 13y ago
As I said here the last time a new React version came out, we're using React for more or less all new JS development at Khan Academy, and we're loving it. Happy to answer questions.
- velikos 13y ago
  What does it give you above other frameworks, specifically Angular?
  - vjeux 13y ago
    Two great posts by Pete Hunt http://pt.reddit.com/r/javascript/comments/1oo1y8/i_know_angularjs_are_there_any_reasons_i_should/ http://pt.reddit.com/r/javascript/comments/1oo1y8/i_know_ang... http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-AngularJS-A-Closer-Look http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-Angu...
  - spicyj 13y ago
    I wrote a little bit about my experiences here: http://benalpert.com/2013/06/09/using-react-to-speed-up-khan-academy.html http://benalpert.com/2013/06/09/using-react-to-speed-up-khan... In short, it's simple (very little to learn) and very fast. One other big thing I love is that it encourages building reusable and composable components. Angular has a lot of the same structure, but if you end up building directives then you have to drop down to manual DOM manipulation again if you want speed.
tegeek 13y ago
Any framework like React (which embeds html tightly with javascript) is flawed at its core. 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.
- peterhunt 13y ago
  Here's my talk from JSConf EU that directly tackles those concerns. http://2013.jsconf.eu/speakers/pete-hunt-react-rethinking-best-practices.html http://2013.jsconf.eu/speakers/pete-hunt-react-rethinking-be...
- brandonbloom 13y ago
  1) I totally disagree about embedding HTML, but it's optional anyway. Cohesion counts. See Pete Hunt's video. 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
  - tegeek 13y ago
    <tabManager background=blue> <tab closeButton=true> Hello {{propertyName}} </tab> </tabManager> 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.
    - jacktoole1 13y ago
      I don't have any practical experience with angular (but I'd like to, and definitely think its testability is a step in the right direction). 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.
    - tallowen 13y ago
      For what its worth, <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 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>
kleiba 13y ago
Damn, from misreading the headline I thought ReactOS had jumped up a few version numbers.
- zpao 13y ago
  Sorry to get your hopes up! I'll try to remember to make it a bit more obvious next time.
dugmartin 13y ago
I just read through all the React docs and the tutorial. My first impression is it looks and reads like Flex for Javascript, both for the JSX markup and the component lifecycle events. I'm not saying that is a bad thing, just an observation.

96 points by zpao 13y ago

As I said here the last time a new React version came out, we're using React for more or less all new JS development at Khan Academy, and we're loving it. Happy to answer questions.

velikos 13y ago
What does it give you above other frameworks, specifically Angular?
- vjeux 13y ago
  Two great posts by Pete Hunt http://pt.reddit.com/r/javascript/comments/1oo1y8/i_know_angularjs_are_there_any_reasons_i_should/ http://pt.reddit.com/r/javascript/comments/1oo1y8/i_know_ang... http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-AngularJS-A-Closer-Look http://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-Angu...
- spicyj 13y ago
  I wrote a little bit about my experiences here: http://benalpert.com/2013/06/09/using-react-to-speed-up-khan-academy.html http://benalpert.com/2013/06/09/using-react-to-speed-up-khan... In short, it's simple (very little to learn) and very fast. One other big thing I love is that it encourages building reusable and composable components. Angular has a lot of the same structure, but if you end up building directives then you have to drop down to manual DOM manipulation again if you want speed.

tegeek 13y ago

Any framework like React (which embeds html tightly with javascript) is flawed at its core. 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.

peterhunt 13y ago
Here's my talk from JSConf EU that directly tackles those concerns. http://2013.jsconf.eu/speakers/pete-hunt-react-rethinking-best-practices.html http://2013.jsconf.eu/speakers/pete-hunt-react-rethinking-be...
brandonbloom 13y ago
1) I totally disagree about embedding HTML, but it's optional anyway. Cohesion counts. See Pete Hunt's video. 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
- tegeek 13y ago
  <tabManager background=blue> <tab closeButton=true> Hello {{propertyName}} </tab> </tabManager> 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.
  - jacktoole1 13y ago
    I don't have any practical experience with angular (but I'd like to, and definitely think its testability is a step in the right direction). 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.
  - tallowen 13y ago
    For what its worth, <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 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>

kleiba 13y ago

Damn, from misreading the headline I thought ReactOS had jumped up a few version numbers.

zpao 13y ago
Sorry to get your hopes up! I'll try to remember to make it a bit more obvious next time.

dugmartin 13y ago

I just read through all the React docs and the tutorial. My first impression is it looks and reads like Flex for Javascript, both for the JSX markup and the component lifecycle events. I'm not saying that is a bad thing, just an observation.