My experience with Meteor is almost zero, but I've read articles about it and its documentation, so I'm talking about by my own experience... I get skeptical when I see a solution promising to solve your problems easily. There is always that moment when you need something more specific and is already implemented by that solution in such a way you can't change it. It sounds like MS Access (in its own proportions).
Probably developers feel a lack of faith on Meteor because of a all-in-one solution like that.
For example, I'd really consider using Meteor for a web site, blog, simple web applications, but not for a complex information system (at least by now). Probably I'm wrong, but this is the way I feel.
The lack of success cases about Meteor being used in big apps doesn't help much.
I completely agree with the statement "when you need something more specific and is already implemented by that solution in such a way you can't change it".
I think many developers are scared away by the nature of Meteor, since it's a complete toolset which doesn't always play well with existing tech. Fortunately they're working on that part, doing stuff like making Meteor work with Angular.
Ricardo Memoria
IT Consultant and developer
My experience with Meteor is almost zero, but I've read articles about it and its documentation, so I'm talking about by my own experience... I get skeptical when I see a solution promising to solve your problems easily. There is always that moment when you need something more specific and is already implemented by that solution in such a way you can't change it. It sounds like MS Access (in its own proportions).
Probably developers feel a lack of faith on Meteor because of a all-in-one solution like that.
For example, I'd really consider using Meteor for a web site, blog, simple web applications, but not for a complex information system (at least by now). Probably I'm wrong, but this is the way I feel.
The lack of success cases about Meteor being used in big apps doesn't help much.