Ask HN: Is Meteor.js dead?
11–20 of 93 posts
Re: Ask HN: Is Meteor.js dead?
#12Re: Ask HN: Is Meteor.js dead?
#13Re: Ask HN: Is Meteor.js dead?
#14We've been doing doubletime to migrate off of an old Meteor app, due to its bundling of old versions of node and really questionable use of Mongo. I think that, in the right hands, Meteor is a great prototyping tool--putting into production and scaling it though is a fool's errand.
Re: Ask HN: Is Meteor.js dead?
#15Technically speaking, Meteor's in the best state it's ever been: latest Node version, full Babel support (zero config), great accounts system, full NPM support, ready-to-go MongoDB support and access to multiple DBs via Apollo. Things like Atmosphere, Meteor's package system—which have been earmarked to be phased out in favor of NPM—get Meteor some negative press.
It's a shame, too, because having actively explored alternatives over the last six months, the only platform that came close to being comparable (in respect to being fully featured out of the box) has been Firebase. It's not the only option but it's a damn good one.
Meteor deserves far more attention that it receives—miscommunication around 2015 regarding Meteor's choice of UI framework and the Meteor Development Group's shift to focus on Apollo put a serious ding in its trajectory. A guess: MDG had to make a return for investors and Meteor itself—and their hosting product, Galaxy—wasn't growing quickly enough (just a guess).
Re: Ask HN: Is Meteor.js dead?
#16does not bode well for any open source software project. there is a vast expanse between "dead dead" and "vivaciously alive". You will not get a straight answer because there is no good answer.
Re: Ask HN: Is Meteor.js dead?
#17Between GraphQL and React, I'm not sure how much Meteor is left in a modern "Meteor" app.
Re: Ask HN: Is Meteor.js dead?
#18Meteor's problems were rooted in its real-time protocol, DDP, which had some problems. Firstly, everything is real-time by default. It's better to minimize the amount of real-time components in your application as there are very few things that need to be real-time. Secondly, the pub-sub caching mechanism made it infeasible for situations with many concurrent users. I was able to get around this by proxying some of their internal functions.
Significant people in the ecosystem started leaving (e.g. Arunoda), probably for the same reasons. AFAIK, it's still the best JavaScript framework out there for prototyping and MVPs. Their accounts system makes whipping up a user-driven application trivial. MDG (the phenomenal team behind Meteor) is likely focusing their efforts on Apollo now, because they understand DDP's shortcomings. If you're interested in Meteor, I suggest looking into Apollo.
Re: Ask HN: Is Meteor.js dead?
#19I built a major project in Meteor last summer, and it was a big mistake. For the most part, Meteor itself is stable and being actively developed, but many of the packages are experiencing severe rot, and one of the developers of a few of the most used meteor packages recently went out of business and took all their documentation down with them.