Sorry but I think people get my intention wrong. I'm not new to react, reactive UIs or components. I have a whole lot of experience with it. I even wrote a piece in how to write your own reactivity system (using vuejs' system as example).
Also, neither components nor reactivity are new. React might be first of its kind but its single parts all existed before. Saying only jquery and backbone where before completely ignores AngularJS, Polymer, EmberJS and others that came before react to solve the biggest problems at the time in frontend development: code organization and coding convenience. React actually goes one step back in being a good tool for UI state management but not delivering any other coder convenience or code structure by default.
React actually goes one step back in being a good tool for UI state management but not delivering any other coder convenience or code structure by default.
This is by design, I believe. React is a library - a minimal set of components just to work with the view layer. Versus Angular and Ember, which are frameworks that include everything under the sun.
But yes, there is no defined structure for a React app. There are best practices, but it's up to you on how you structure your app. I think a lot of devs like this flexibility over something like Angular or Ember's opinionated defaults.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sorry but I think people get my intention wrong. I'm not new to react, reactive UIs or components. I have a whole lot of experience with it. I even wrote a piece in how to write your own reactivity system (using vuejs' system as example).
Also, neither components nor reactivity are new. React might be first of its kind but its single parts all existed before. Saying only jquery and backbone where before completely ignores AngularJS, Polymer, EmberJS and others that came before react to solve the biggest problems at the time in frontend development: code organization and coding convenience. React actually goes one step back in being a good tool for UI state management but not delivering any other coder convenience or code structure by default.
This is by design, I believe. React is a library - a minimal set of components just to work with the view layer. Versus Angular and Ember, which are frameworks that include everything under the sun.
But yes, there is no defined structure for a React app. There are best practices, but it's up to you on how you structure your app. I think a lot of devs like this flexibility over something like Angular or Ember's opinionated defaults.