News for hackers. Stuff that matters.
Re:The State of Meteor Part 2: What Happens Next by matthewrudy on Wednesday January 20, 2016 @10:01PM (#10943076)
Meteor's best trick has always been data synchronization.

That was the magic trick that sold your client.

They proved real-time data synchronization could be simple and seamless, and everyone else had to run to catch up.

But that trick is now 4 years old, and nothing else of substance really emerged.

As Ember, Angular and React grew, you were never going to want to use their odd looking front end.

Their data sync also came with dubious claims to scalability, not the least is their tie to Mongo.

That may be fixed now, but the consequence is being tied into Meteor Galaxy.

Meteor should have thrown everything away, and become just the data layer.

Like Firebase, but open source, and backend / datastore agnostic.

They tried to standardise DDP, but it didn't catch on.

But what the world needs is a standard like GraphQL, but handling data updates, and with automatic realtime data sync.

Thatd be a wonderful legacy for Meteor.

But this won't happen, as the company needs to make money from hosting.

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!
Re:The State of Meteor Part 2: What Happens Next by richsilv on Thursday January 21, 2016 @08:32AM (#10945016)
You're not in any way tied to Galaxy. Meteor is just a node process under the hood, so you can run it (and likewise your MongoDB) wherever you want. Tools like Meteor Up make it very easy to do so on your choice of VM.

What that says about MDG's business model is less clear.

Re:The State of Meteor Part 2: What Happens Next by huula on Thursday January 21, 2016 @03:41AM (#10944085)
Completely agree! Hope Meteor community would seriously consider this.