5 ms·

"battle-hardened", yet churns drastically every release? You and I have different ideas of what battle hardened means.

danabramov 11y ago
Can you please help me understand the issue by providing a specific example of how a new React release introduced churn in your project?
- goldbrick 11y ago
  Sure, I started a react project and got everything working with es6 and babel in October. In December I upgraded to react 0.14 and had to refactor all the things. It was extremely difficult to figure out how to solve some of the arbitrary-seeming changes, such as now having to re-bind all of the methods in the constructor.
  - danabramov 11y ago
    Wait, why did you refactor all things? I’m afraid you have been misinformed. :-( Please read the official release notes when upgrading. Nowhere does 0.14 say you need to change components to use classes. They are allowed now (since 0.13) but React.createClass() is still there and is not going away any time soon. I’m afraid you listened to bad advice.
    - goldbrick 11y ago
      I was already using es6 classes so I didn't have the choice. I couldn't get 0.14 to work otherwise.
      - danabramov 11y ago
        Not sure I understand you. You are saying that 1. Transitioning to 0.14 forced you to rewrite something (what? how? I assumed you meant transitioning to ES6 classes which wasn’t necessary but it seems like you meant something else) 2. What choice was it that you didn’t have? Just like 0.13, 0.14 (and 15 soon) allows you to use either ES6 classes or React.createClass(). Both approaches work and will keep working. What are you referring to? It would really help if you could share at least a simple code example demonstrating your pain points. I want to help! Cheers.
aidenn0 11y ago
I have a react app that is almost 2 years old now and the only change I had to make was when they moved a function from the React to the ReactDOM namespace.
- goldbrick 11y ago
  It wouldn't happen to be open source then would it? Perhaps I'm just React-ing wrong.
  - aidenn0 11y ago
    It is, but it's not written in javascript[1]. Flux came out when I was in the middle of developing it, and I spent hours reading about it, looking at it and playing with it, and it just didn't solve any problems that I had. Note that the community's ideas of best-practices, and all of the ecosystem around react is changing at an absurd pace, but core react is fairly stable. 1: https://github.com/jasom/cl-fccs https://github.com/jasom/cl-fccs

Can you please help me understand the issue by providing a specific example of how a new React release introduced churn in your project?

goldbrick 11y ago
Sure, I started a react project and got everything working with es6 and babel in October. In December I upgraded to react 0.14 and had to refactor all the things. It was extremely difficult to figure out how to solve some of the arbitrary-seeming changes, such as now having to re-bind all of the methods in the constructor.
- danabramov 11y ago
  Wait, why did you refactor all things? I’m afraid you have been misinformed. :-( Please read the official release notes when upgrading. Nowhere does 0.14 say you need to change components to use classes. They are allowed now (since 0.13) but React.createClass() is still there and is not going away any time soon. I’m afraid you listened to bad advice.
  - goldbrick 11y ago
    I was already using es6 classes so I didn't have the choice. I couldn't get 0.14 to work otherwise.
    - danabramov 11y ago
      Not sure I understand you. You are saying that 1. Transitioning to 0.14 forced you to rewrite something (what? how? I assumed you meant transitioning to ES6 classes which wasn’t necessary but it seems like you meant something else) 2. What choice was it that you didn’t have? Just like 0.13, 0.14 (and 15 soon) allows you to use either ES6 classes or React.createClass(). Both approaches work and will keep working. What are you referring to? It would really help if you could share at least a simple code example demonstrating your pain points. I want to help! Cheers.

aidenn0 11y ago

I have a react app that is almost 2 years old now and the only change I had to make was when they moved a function from the React to the ReactDOM namespace.

goldbrick 11y ago
It wouldn't happen to be open source then would it? Perhaps I'm just React-ing wrong.
- aidenn0 11y ago
  It is, but it's not written in javascript[1]. Flux came out when I was in the middle of developing it, and I spent hours reading about it, looking at it and playing with it, and it just didn't solve any problems that I had. Note that the community's ideas of best-practices, and all of the ecosystem around react is changing at an absurd pace, but core react is fairly stable. 1: https://github.com/jasom/cl-fccs https://github.com/jasom/cl-fccs