Re:Application Architecture with React: Rethinking Flux
by gedy on Monday September 14, 2015 @12:10PM
(#10215772)
Maybe it's just my peers :-) but this highlights to me why I've been reluctant to adopt React. I keep getting eye rolls about not using it - but everyone I encounter seems to in the process of still figuring out application and architecture basics? We weren't an Angular shop, so never had the problems that React seems to target with one-way, etc.
[ Parent
| on HN ]
Re:Application Architecture with React: Rethinking Flux
by grandalf on Monday September 14, 2015 @12:55PM
(#10216035)
It takes a while to get a sense of appropriate component boundaries. Like other decisions, this involves tradeoffs.
I've found that I sometimes err in the direction of making components too granular, when this makes the data flows more complex.
Boundaries should exist for encapsulation, but also for change management, reusability, and interfacing with data.
Yes, components can be misused.
I've found that codebases such as rails apps often have so much boilerplate and blind following of conventions (equating to many, many lines of code) that the more fundamental issues like flawed domain modeling or incorrect abstractions are rarely even considered a problem.
Re:Application Architecture with React: Rethinking Flux
by gedy on Monday September 14, 2015 @01:19PM
(#10216152)
Yes true, and to be clear, I think React is fine on it's own. It's just that from my view it's not fundamentally so superior as to warrant rewriting a decently structured app written in one of the other JS frameworks from the past few years. Especially if folks then go and have to reinvent/relearn, well, everything.
A lot of "React" excitement folks shared with me had more to do with using Webpack and ES6, which you can use with other frameworks.