Where do we go from here?
Meteor and I carried on like the best of friends building apps for clients that I could have only dreamed of just 6 months earlier. On October 28, 2014 MDG released Meteor 1.0! It was a momentous occasion for everyone in the Meteor community and I even got a sweet T-shirt at World Wide Meteor Day which I wear to this day. It was a very exciting time to be a Meteor developer.
Since then I have experimented with (and started using) other technologies too: React, Neo4j, Webpack, and now Apollo, and I have started to wonder: If I’m not using Meteor’s build system, or data layer, or real-time data, or MongoDB… why am I using Meteor at all?
Questioning my relationship with Meteor has been difficult for me. I’ve been so closely intertwined with Meteor over the last 2 years building apps, advocating Meteor, and getting involved with the developer community that it feels almost like I’m turning on a close friend. It’s not unlike how I’ve felt in the past when I’ve realized that it’s time to break up with a girlfriend that I still care for, but just don’t see a future with.
After I finish this post I’m going to be checking out FeathersJS for the first time. I’ve read the docs several times between doing other things and it looks really interesting! The fact that it’s just a “thin layer on top of Express” makes it attractive to me too. As I’ve grown as a developer my interest in getting closer to the metal has grown too.
For right now, I’m not breaking up with Meteor, but I’m definitely considering our future together. I still love the experience of using the platform, but I’m just not sure that it’s what I need going forward. Maybe things will get better as Meteor matures and changes, but I don’t know if I’m willing to wait around.
I’ll leave you with some Alan Parsons for your listening pleasure.
Please let me know what you think in the comments. Are you using Meteor? Were you using Meteor and have moved on?