Application Architecture with React: Rethinking Flux

Re:Application Architecture with React: Rethinking Flux by jeswin on Monday September 14, 2015 @10:28AM (#10215214)

I wish Meteor nothing but the best, but React is no longer just a UI framework. Relay encroaches significantly on Meteor turf; and its optimistic update mechanism is arguably more flexible that Meteor's syncing protocol. In addition, there's React native and deep integration with tools such as Flow and Include.

There should be space for Meteor and I don't mean to be discouraging, but this is generally a good time for framework authors to internally debate how the competitive landscape has changed and the best path forward.

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by btown on Tuesday September 15, 2015 @01:25AM (#10219079)

Unfortunately, Relay is significantly further from "just working" with push and write-once-run-everywhere-including-your-database query language, than Meteor is from "just working" with React. If you want a realtime immediate-mode-rendered web application without writing tons of boilerplate for data handling, and duplicating business logic in your server (i.e. GraphQL implementation) and client, Meteor+React has the edge today. You're right, though, that frameworks built on Relay+React will eventually catch up. I'm also looking forward to that day.

[ Parent | on HN ]