News for hackers. Stuff that matters.

A comment on A Primer for Building Single Page Applications with React. Parent comment

Re:A Primer for Building Single Page Applications with React by BinaryIdiot on Tuesday March 24, 2015 @10:07PM (#9260875)
> I agree, but if we're talking about using a front-end framework like React here, wouldn't that mean we're only talking about the UI parts of the application anyway?

I don't think so; when working on code for a web application there is always code, styling and html elements that deal ONLY with the presentation side of it but then there is also code that handles talking to the backend, negotiating with web sockets, etc. That code really needs to be separated and what I'm referring to.

> the people behind React do make reasonable arguments in favour of their more component-based separation of concerns.

I love component based separations and I get the feeling many of us are talking about similar things.

[ Parent | on HN ]
Re:A Primer for Building Single Page Applications with React by Silhouette on Tuesday March 24, 2015 @11:16PM (#9261072)
I don't think so; when working on code for a web application there is always code, styling and html elements that deal ONLY with the presentation side of it but then there is also code that handles talking to the backend, negotiating with web sockets, etc. That code really needs to be separated and what I'm referring to.

Right, but React isn't normally used for things like back-end comms. It's often loosely described as being for the "V" in "MVC", which makes sense given the whole declarative specification of DOM content angle and the one-way data binding style.

[ Parent | on HN ]