React v0.14 • Hacker News Board

Re: React v0.14

#21

Post by drinchev » Wed, Oct 07, 2015, 6:52 PM UTC

React is cool. Switching to React helped me do :

1. Get rid of any jquery-like library.

2. Get rid of my HTML/Handlebars files :)

3. Generate dynamic CSS classNames for my components allowed me to get rid of stylesheets naming conventions / strategies ( BEM, etc. )

4. With the help of Flux ( yahoo's implementation ) I got rid of writing two code-bases ( front-end / back-end ). Now I'm putting everything in one place, this is awesome! ( I did it with server-side rendering, so I didn't loose anything at all )

Re: React v0.14

#22

Post by draw_down » Wed, Oct 07, 2015, 6:54 PM UTC

Touche wrote: post #9

> Like always, we have a few breaking changes in this release. We know changes can be painful (the Facebook codebase has over 15,000 React components), so we always try to make changes gradually in order to minimize the pain. Since React is a semver project, from the website: > How do I know when to release 1.0.0? > If your software is being used in production, it should probably already be 1.0.0. If you have a stabl…

Is it a semver project? Doesn't seem like one, the whole idea is to raise major version when you break compatibility.

Re: React v0.14

#23

Post by draw_down » Wed, Oct 07, 2015, 6:54 PM UTC

losvedir wrote: post #12

The enthusiasm around React is infectious and I'm thinking about integrating it into one of my projects but I can't quite tell what exactly it's supposed to be used for. Is it only for SPAs or is it reasonable to consider react when you just want to add some interactions and dynamism to a page that was rendered server side? React seems kind of like an all-or-nothing approach. It seems like overkill if you just want t…

It's an idea for organizing the components of user interfaces, regardless of the platform.

Re: React v0.14

#24

Post by epmatsw » Wed, Oct 07, 2015, 6:55 PM UTC

eric-hu wrote: post #17

Touche wrote: post #9

> Like always, we have a few breaking changes in this release. We know changes can be painful (the Facebook codebase has over 15,000 React components), so we always try to make changes gradually in order to minimize the pain. Since React is a semver project, from the website: > How do I know when to release 1.0.0? > If your software is being used in production, it should probably already be 1.0.0. If you have a stabl…

I came in here to comment on this. React sounds exciting from what I've read about it, but I didn't realize it was pre-1.0. To teams who are using it in production, did you talk about this? What are arguments for using it despite it not being 1.0?

We're migrating from Backbone to React, and it's been lovely. Our main argument is essentially what the grandparent said: based on the policies React has been following, it basically behaves like a 1.0 release. There's clear deprecation warnings and announcements, and those are caught by our test suite. The only backwards-incompatible changes that have happened since we started using it earlier this year have been mostly painless Ctrl+F fixes, and even the bigger ones (ReactDOM, etc.) have not been too much of a problem. And from a logical perspective, if it's stable enough for Facebook (Alexa #2) to use for production, it's stable enough for a smallish HR software company.

Re: React v0.14

#25

Post by drinchev » Wed, Oct 07, 2015, 6:55 PM UTC

eric-hu wrote: post #17

Touche wrote: post #9

> Like always, we have a few breaking changes in this release. We know changes can be painful (the Facebook codebase has over 15,000 React components), so we always try to make changes gradually in order to minimize the pain. Since React is a semver project, from the website: > How do I know when to release 1.0.0? > If your software is being used in production, it should probably already be 1.0.0. If you have a stabl…

I came in here to comment on this. React sounds exciting from what I've read about it, but I didn't realize it was pre-1.0. To teams who are using it in production, did you talk about this? What are arguments for using it despite it not being 1.0?

There's something wrong these days with version argumentations and reasoning.

TypeScript is version 1.6, which was released when Node was 0.12 and includes React 0.13 support of JSX files.

So I'm not sure anyone puts a reason behind version numbers anymore.

Re: React v0.14

#26

Post by aaronkrolik » Wed, Oct 07, 2015, 6:55 PM UTC

losvedir wrote: post #12

The enthusiasm around React is infectious and I'm thinking about integrating it into one of my projects but I can't quite tell what exactly it's supposed to be used for. Is it only for SPAs or is it reasonable to consider react when you just want to add some interactions and dynamism to a page that was rendered server side? React seems kind of like an all-or-nothing approach. It seems like overkill if you just want t…

Interesting you draw the Knockout comparison. I'm pretty new to React, but have done a fair amount with Knockout. I find that I use the two in very similar ways. I know knockout has a large feature set and claims to be a VMMV (whatever that means), but in practice I used it mostly to go between some dynamic JSON and DOM.

Re: React v0.14

#27

Post by sebmarkbage » Wed, Oct 07, 2015, 6:56 PM UTC

clessg wrote: post #3

A lot of great ideas in this release and it makes me excited for the future of React. I've been on 0.14-rc1 and my favorite feature so far is stateless function components. So much cleaner than class-based components. One downside is that hot reloading doesn't work with it yet (AFAIK). Hopefully that will come soon now that 0.14 is officially released. (And I believe Dan is/was on vacation.) Andrew Clark (core contri…

Note that the stateless part is mostly just a stepping stone to a stateful variant.

https://github.com/reactjs/react-future/tree/master/07%20-%2...

Re: React v0.14

#28

Post by williamcotton » Wed, Oct 07, 2015, 6:58 PM UTC

eric-hu wrote: post #17

Touche wrote: post #9

> Like always, we have a few breaking changes in this release. We know changes can be painful (the Facebook codebase has over 15,000 React components), so we always try to make changes gradually in order to minimize the pain. Since React is a semver project, from the website: > How do I know when to release 1.0.0? > If your software is being used in production, it should probably already be 1.0.0. If you have a stabl…

I came in here to comment on this. React sounds exciting from what I've read about it, but I didn't realize it was pre-1.0. To teams who are using it in production, did you talk about this? What are arguments for using it despite it not being 1.0?

What's in a name? That which we call a rose by any other name would smell as sweet.

Re: React v0.14

#29

Post by epmatsw » Wed, Oct 07, 2015, 6:58 PM UTC

aaronkrolik wrote: post #19

I'm fairly new to react, and have wondered if I was using it correctly (as intended). Almost always I have a root component that manages state, passing it to children via props. All changes to state go through that root component, either by callback (also passed as prop) or some external event. Is this update in a sense validation of that approach?

What you've described is pretty similar to Flux or one of its variants. The main difference would be that instead of managing state inside of the root component via setState, you have an external state ("store"), which would handle the state logic and provide the appropriate values as props to the root component. So yes, it sounds like you're doing it "right".

Re: React v0.14

#30

Post by williamcotton » Wed, Oct 07, 2015, 7:01 PM UTC

losvedir wrote: post #12

The enthusiasm around React is infectious and I'm thinking about integrating it into one of my projects but I can't quite tell what exactly it's supposed to be used for. Is it only for SPAs or is it reasonable to consider react when you just want to add some interactions and dynamism to a page that was rendered server side? React seems kind of like an all-or-nothing approach. It seems like overkill if you just want t…

Is it only for SPAs?

Here's an example of a web application built with React, Express and Browser Express that defines the same UI components and routes for both the server and the browser:

https://github.com/williamcotton/universal-react