News for hackers. Stuff that matters.
Re:The State of Meteor Part 2: What Happens Next by dfischer on Thursday January 21, 2016 @12:55AM (#10943623)
GraphQL and Relay may be the answer but it's too young to make that switch now and Meteor is solving that exact problem. Meteor has the momentum and community to take it further. Maybe it actually adopts the GraphQL standard and unifies it into the ultimate dev UX experience.
Re:The State of Meteor Part 2: What Happens Next by pacnw on Thursday January 21, 2016 @09:14AM (#10945237)
Yeah, I went down the Relay/GraphQL rabbit hole for a good 1.5 months last year, but unfortunately there is a tremendous amount of work to set up GraphQL servers to even get your data out to Relay, and it is not real-time at the moment (although the 'community' appears to be work on it. I so wish Meteor would provide a drop-in module for just the DDP, I don't even care if its Mongo, their real-time subscription works.
Re:The State of Meteor Part 2: What Happens Next by matthewrudy on Thursday January 21, 2016 @05:01AM (#10944286)
It might happen, and the next year or so will decide its fate. Exciting!