I'm not sure if this really warrants a reply, but I did want to correct the record. Even if you think Meteor "crashed and burned", it was definitely not a flash in the pan. It was launched in 2012 and seven years later there's still a small but active community. Many successful companies have used Meteor at some point, and many still do.
I think that the fact you think it was a "framework du jour" just highlights how much potential –and yes, hype– it had in its heyday. It may not quite have lived up to that hype, but it certainly accomplished more than the vast majority of web frameworks.
Maybe you could try giving arguments. Their tracker reactivity system is much like what react hooks now is. They had zero config build tool, much like what parcel now tries to be. They had a package system that because of it's SAT solver is way better for frontend code, something that took NPM years (and still isn't great). It's still the most convenient way to have a type of reactive queries I knoe about... And all of they basically already had in 2011 and all changes thry introduced since then were mostly backwards compatible.
Any technology that had success like Meteor cannot, in good faith, be called bad. All technology have their pros and cons, and Meteor was the appropriate choice in a number of ways, especially a few years ago.
