I think part of the problem is the Meteor team's reluctance to have Meteor thought of or even used as a traditional web framework.
Their vision is a framework for real-time applications that allows you to develop for web and mobile in parallel, but that puts them in a category where their intended use case is invariably losing to native every time. I think there are a lot of people who would love to use Meteor for RESTful mobile-first web application development, but are a little disappointed when they find Meteor is MongoDB-first and doesn't even have native support for routing.
For me, Meteor currently occupies a strange space where it's the web framework I'm the most excited about, yet it's the wrong tool for every project idea I have.