Used meteor to try and build a production ready project management app in a company I was employed at years ago. We never got it off the ground and this is one of those rare times that technology was the direct reason we couldn't make the product work.
Meteor was great for quick and dirty apps but beyond that meteor never made it past the feeling that it was a prototype itself.
Everything about data management was painful the moment you started to deal with production related use cases. Unrelated changes to nested fields would propagate changes up the chain which would in turn trigger data refreshes of entire collections. And the documentation never helped here. The documentation was only about the minimum needed to perform a task, but for all their talk of opinionated frameworks, the community had to come up with their own opinions on how to actually use the framework efficiently.
Overall it was a dumpster fire but it had a positive effect on me since I was early in my career. I learnt how to better evaluate technology to actually understand whether the tools were truly production stable ready and more importantly if the documentation and community were also "production ready". So I guess I'm kind of grateful that meteor happened to me. ¯\_(ツ)_/¯
Very much agree with you on this. I picked up a live Meteor app that felt very much like it had been built as a prototype that had been built upon into a production app. It was a mess, it had clearly evolved over time and over multiple Meteor releases, there was no obvious structure at all - just felt like a bunch of files that were all loaded into some soup that became the app.
I don't think Meteor ever had decent docs on going from the prototype stage to a fully fledged application and how you'd evolve the structure over the time.
I could name a lot of problems I've had with Meteor, and I definitely agree with having a proper evaluation of tech before using it - knowing the limits of the stack you choose and if it's going to lock you in in the long term.
It's felt like a framework that hasn't been given time needed recently to keep it up to date, improving docs etc as MDG have shifted their focus on Apollo.
Meteor was great for quick and dirty apps but beyond that meteor never made it past the feeling that it was a prototype itself.
Everything about data management was painful the moment you started to deal with production related use cases. Unrelated changes to nested fields would propagate changes up the chain which would in turn trigger data refreshes of entire collections. And the documentation never helped here. The documentation was only about the minimum needed to perform a task, but for all their talk of opinionated frameworks, the community had to come up with their own opinions on how to actually use the framework efficiently.
Overall it was a dumpster fire but it had a positive effect on me since I was early in my career. I learnt how to better evaluate technology to actually understand whether the tools were truly production stable ready and more importantly if the documentation and community were also "production ready". So I guess I'm kind of grateful that meteor happened to me. ¯\_(ツ)_/¯