3 ms·

It seems like all the recent client-side frameworks are really desperate to jump on the React bandwagon somehow. I suppose this could be seen as validation tha

by robbles 12y ago

It seems like all the recent client-side frameworks are really desperate to jump on the React bandwagon somehow. I suppose this could be seen as validation that the new approach it takes to rendering and organizing UI is a good one, if competing frameworks are trying to mimic or integrate with it.

jtblin 12y ago
Do you have any references about that?
EdwardDiego 12y ago
I'm looking at React now, as our first experience of Angular had a really steep learning curve, and it's going to be a hard sell to our UI team who have been writing Wicket for a long time - we're moving away from Wicket in some areas as it doesn't handle complex dynamic UI very well. It's got the AJAX support if you don't mind a trip back to the server for every state change, but when it goes wrong, the debugging gets really hairy. React's component orientations look at little easier to pick up and get going with, and it'll be a lot more familiar feeling to our UI team who have been passing data down a tree of components for some time now. However, I have yet to build anything substantial in it, but so far I'm hopeful (I shall disregard Flux for now, we may not require its complexity just yet). The data binding all looks to be one way, and each component looks testable in its own right. So hopefully I'm not just jumping on yet another bandwagon.
- pbowyer 12y ago
  Have you considered EmberJS as an alternative? React may be the best thing since sliced bread, but as Rich Harris, author of Ractive, writes [1]: > Ractive uses similar techniques to Glimmer - it parses the template into a structure such that it's very easy to identify which DOM nodes need to be updated when data changes. This is different to how React (for example) handles DOM updates, which involves re-rendering everything and then running a diff. > The two approaches both have the same goal - minimising DOM updates - but go about it in very different ways. Each has advantages and disadvantages, and I believe we're going to develop a much clearer understanding of what they are in 2015. 1. https://github.com/rich-harris/ractive-dbmonster https://github.com/rich-harris/ractive-dbmonster
  - EdwardDiego 12y ago
    > Have you considered EmberJS as an alternative? I haven't, but I'll have a look now. Cheers. :)
primigenus 12y ago
If your comment is in response to the linked article: 1. Meteor isn't a client-side framework, it's a full-stack platform; 2. This post was written by a member of the community, not someone on the core team, so I don't think you can say "desperate to jump on the React bandwagon" If this isn't what you meant, ignore my post, just wanted to mention those two things :)
- robbles 12y ago
  Both good points. I didn't realize that this wasn't written by someone not on the core team. As previous responses have shown, I didn't think through this comment too well. Just trying to articulate a feeling I had about a lot of recent posts regarding React, but it looks like it doesn't really pertain to this article.

by robbles 12y ago

jtblin 12y ago

Do you have any references about that?

EdwardDiego 12y ago

I'm looking at React now, as our first experience of Angular had a really steep learning curve, and it's going to be a hard sell to our UI team who have been writing Wicket for a long time - we're moving away from Wicket in some areas as it doesn't handle complex dynamic UI very well. It's got the AJAX support if you don't mind a trip back to the server for every state change, but when it goes wrong, the debugging gets really hairy. React's component orientations look at little easier to pick up and get going with, and it'll be a lot more familiar feeling to our UI team who have been passing data down a tree of components for some time now. However, I have yet to build anything substantial in it, but so far I'm hopeful (I shall disregard Flux for now, we may not require its complexity just yet). The data binding all looks to be one way, and each component looks testable in its own right. So hopefully I'm not just jumping on yet another bandwagon.

pbowyer 12y ago
Have you considered EmberJS as an alternative? React may be the best thing since sliced bread, but as Rich Harris, author of Ractive, writes [1]: > Ractive uses similar techniques to Glimmer - it parses the template into a structure such that it's very easy to identify which DOM nodes need to be updated when data changes. This is different to how React (for example) handles DOM updates, which involves re-rendering everything and then running a diff. > The two approaches both have the same goal - minimising DOM updates - but go about it in very different ways. Each has advantages and disadvantages, and I believe we're going to develop a much clearer understanding of what they are in 2015. 1. https://github.com/rich-harris/ractive-dbmonster https://github.com/rich-harris/ractive-dbmonster
- EdwardDiego 12y ago
  > Have you considered EmberJS as an alternative? I haven't, but I'll have a look now. Cheers. :)

primigenus 12y ago

If your comment is in response to the linked article: 1. Meteor isn't a client-side framework, it's a full-stack platform; 2. This post was written by a member of the community, not someone on the core team, so I don't think you can say "desperate to jump on the React bandwagon" If this isn't what you meant, ignore my post, just wanted to mention those two things :)

robbles 12y ago
Both good points. I didn't realize that this wasn't written by someone not on the core team. As previous responses have shown, I didn't think through this comment too well. Just trying to articulate a feeling I had about a lot of recent posts regarding React, but it looks like it doesn't really pertain to this article.