5 ms·
I agree, and I wish more JS projects in general would embrace SQL. I think part of the problem is the Meteor team's reluctance to have Meteor thought of or eve
by chjohasbrouck 11y ago
I agree, and I wish more JS projects in general would embrace SQL.
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.
- deleted 11y ago[deleted]
- benaiah 11y ago> 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. You've precisely captured a sentiment that I've been feeling but unable to express for some time. I think Meteor has tremendous potential, but there are a few very problematic issues, coupled with a severely walled ecosystem (Angular also has this problem, React I'm not so sure of but it seems to have it less) and unclear best practices (React has this in spades).