4 ms·
If you have to architect your project around the use of this "library" then it smells a lot more like a framework.
by wvenable 10y ago
If you have to architect your project around the use of this "library" then it smells a lot more like a framework.
- JamesMcMinn 10y agoYou don't architecture you project around React - you simply fit react in wherever you want to render the UI. React has a very small API, most of which are simple lifecycle methods for dealing with changes in the state of a component [1]. You tell React that you'd like to Render component X inside DOM element Y, and that's really all React does. There's no architecturing your project around React. [1] https://facebook.github.io/react/docs/react-component.html https://facebook.github.io/react/docs/react-component.html
- yangbo 10y agoEven though, the number of React's API is still larger than [Binding.scala's API](https://static.javadoc.io/com.thoughtworks.binding/binding_2.11/10.0.2/com/thoughtworks/binding/Binding.html https://static.javadoc.io/com.thoughtworks.binding/binding_2...).
- thatswrong0 10y agoYou will want an application architecture if you're writing a complex project with any view library. React isn't special in this regard.
- wvenable 10y agoAgreed. It's only special because some people want to call it a library instead of a framework.
- thatswrong0 10y agoThat's because it _is_ a library. If you compare it to something like Ember, it's pretty obvious that's what it is.
- jaredklewis 10y agoThe architecture of any web application will be affected by your view layer, whether it is react, custom built, or any thing else. Yes, if use react, you need an architecture compatible with the reactive paradigm.