Hacker News new | ask | show | jobs
by resca79 4251 days ago
When the first release of meteor came out, I was really impressed by the product. The real time update of the web page with zero code was an amazing feature. Today why I need of Meter?

Server side I have multiple choices that guarantee me heigh scalability, performance, and real time. Also the mongodb solo option, without sql is very restrictive.

Client side, there are great js frameworks like React, Ember and Angular that are great modular libraries.

1 comments

I hoped they change meteor and opened it to other databases. The mongodb only option was the reason for us to stop using meteor.

Most of our customer projects use "old school" sql and only a few nosql-databases.

Waiting for Version 2 ;-)

SQL support is on the roadmap [1], along with other great features [2]. By the way, it is also possible to use Meteor mostly for the backend and use a framework like React or Angular for the frontend, although I don't know if there are big advantages with such a setup.

I think Meteor is a great concept because of their seven principles [3], which I haven't seen in any other framework. I haven't worked with Meteor yet but will start a project in short term which uses Meteor, so I'm very excited to see how this works out.

[1] https://trello.com/c/Gf6YxFp2/42-sql-support

[2] https://trello.com/b/hjBDflxp/meteor-roadmap

[3] https://docs.meteor.com/#/basic/sevenprinciples

I'm not really confident about new version the releasing of version 1 was too long. Also I do not see a strong open community that support them like Rails, Django o Node. Of course I wish them to grow in terms of contributors
There is a pretty distinct and active Meteor community, though from the outside it's hard to tell how much of that is just people who are interested in it because of the hype (kinda the problem MongoDB had) vs people who actually use it and know what they are doing.

I wouldn't say the wait for 1.0 is a good indicator of stability or success, though. Node.js is still at 0.x and so is React. AngularJS took a long while to get to 1.x but is now actively working on 2.0.

Many developers are cautious about when they dare calling a product 1.0. Until the idea that "if your code is in production, it's already 1.0" gained some ground, there was barely any code on npm that wasn't stuck in pre-1.0 land.

The real indicator is how much time passes between minor or bugfix releases. Ideally the latter should happen fairly regularly and the former not too often. If Meteor hits 2.0 anytime soon, that could be a worse sign than if it sticks with 1.0.x for "too long".

There is this tiny detail about Meteor, that is has been funded $11.2 million.

- https://www.meteor.com/blog/2012/07/25/meteors-new-112-milli...

- http://venturebeat.com/2012/07/25/meteor-funding/