4 ms·

React is absolutely incredible! They only thing i'd ask for is better support for mobile applications. Namely, touch gestures (tap, swipe, pinch, etc). Since re

by jholly 13y ago

React is absolutely incredible! They only thing i'd ask for is better support for mobile applications. Namely, touch gestures (tap, swipe, pinch, etc). Since react uses synthetic events, perhaps pointer-events can be baked right in so that it's backwards compatible, replacing touch* events.

nebstrebor 13y ago
I've done sufficient with both Angular and React to have decided to go with React for next our project. Its a better fit for this particular project because the "reusable components" paradigm fits what we're doing, which includes building a non-model-specific framework that we can reuse for different models, where the framework renders slightly differently based on meta data provided with the model. We'll probably use Backbone for the model (& meta) & router. I like Angular, and would like to use it for a project that's more concrete and less meta.
- jholly 13y ago
  Something about Angular rubs me the wrong way. I think it has to do with dirty checking. Either that or the scope magic that happens. React, comparatively, is quite straight forward. I hope it stays that way, a minimal API and no magic. The more I look into react the more I wonder if some intermediary representation of the DOM ought to be standardized so that a native "diff/batch" algorithm can be provided as regular functions. I think react would help this cause if it can break up into several projects (react-events, react-virtual-dom, react-dom-diff/batch, etc). Perhaps other projects can adopt parts of react into their own frameworks. Just a thought.
  - jordwalke 13y ago
    Core team member here. That's excellent feedback and we are definitely going to be pushing in that direction where we can. API simplicity will always be a primary goal and a modular core implementation will help advancement of mobile support and testability. The event system is already self contained and shouldn't depend on anything in React at all.
  - AdrianRossouw 13y ago
    I had the same feeling as you. I became ok with it after I realized it could be removed in the future. http://daemon.co.za/2014/03/why-wrong-to-be-afraid-angular http://daemon.co.za/2014/03/why-wrong-to-be-afraid-angular I am looking forward to trying react though, because of how well it plays with backbone (which is still my preference)
peterhunt 13y ago
We do have a tap event plugin in our addons build, but we could definitely use more on this front :)

by jholly 13y ago

nebstrebor 13y ago

I've done sufficient with both Angular and React to have decided to go with React for next our project. Its a better fit for this particular project because the "reusable components" paradigm fits what we're doing, which includes building a non-model-specific framework that we can reuse for different models, where the framework renders slightly differently based on meta data provided with the model. We'll probably use Backbone for the model (& meta) & router. I like Angular, and would like to use it for a project that's more concrete and less meta.

jholly 13y ago
Something about Angular rubs me the wrong way. I think it has to do with dirty checking. Either that or the scope magic that happens. React, comparatively, is quite straight forward. I hope it stays that way, a minimal API and no magic. The more I look into react the more I wonder if some intermediary representation of the DOM ought to be standardized so that a native "diff/batch" algorithm can be provided as regular functions. I think react would help this cause if it can break up into several projects (react-events, react-virtual-dom, react-dom-diff/batch, etc). Perhaps other projects can adopt parts of react into their own frameworks. Just a thought.
- jordwalke 13y ago
  Core team member here. That's excellent feedback and we are definitely going to be pushing in that direction where we can. API simplicity will always be a primary goal and a modular core implementation will help advancement of mobile support and testability. The event system is already self contained and shouldn't depend on anything in React at all.
- AdrianRossouw 13y ago
  I had the same feeling as you. I became ok with it after I realized it could be removed in the future. http://daemon.co.za/2014/03/why-wrong-to-be-afraid-angular http://daemon.co.za/2014/03/why-wrong-to-be-afraid-angular I am looking forward to trying react though, because of how well it plays with backbone (which is still my preference)

peterhunt 13y ago

We do have a tap event plugin in our addons build, but we could definitely use more on this front :)