Time for a Community Fork?

[aadams]

@ralof

I suddenly find myself with tons of work that does not drive my own projects forward.

I feel you bro. I’m in the exact same situation. It really hurts my bottom line to have built something up, just to have to tear part of it down and again and start over because the company behind the tech had a change of mind.

@ralof

There is some various suggested fixes by people outside the team but since there’s no “Oh, we will fix this” from the team, I assumed they did not care. There were also comments indicating that the team are looking at a completely different solution.

This might foreshadow what’s to come once the various part of Meteor-classic become the community’s responsibility. For example this correspondence:

@Siyfion

I feel like the Express, Koa, etc. people have more up-to-date packages for Apollo than we do for Meteor, which is a bit of a shame.

EDIT: GitHub - apollographql/meteor-integration: 🚀 meteor add apollo · GitHub this is the package I am referring too.

@sashko

The Apollo integration packages for React, Angular, etc. are community-maintained. It looks like that model hasn’t worked out as well for the Meteor integration, so we need to find someone who has more time to maintain it.

@Siyfion are you planning on using Meteor + Apollo in production? If so, I’d be happy to work together with you to ensure the Meteor integration stays up to date!

@sashko

Perhaps we should go back to the previous state, which was that we just had a few lines of code you could copy-paste from the docs to do your own integration.

I think the safe bet for my business is to migrate to Facebook’s React, but I don’t know if I have the time and wherewithal to make the jump at this point. I’ve taken the first steps, but now I find out I have to rip out Iron Router with replace it with whoknowswhat, and so on.