Earlier quoted context omitted.
sadly, meteor uses mongo and only mongo. And we are using meteor (which is based on node) Two levels: node and mongo == two levels of sadness. (let the flames commence)
Aah interesting, I have been planning to give meteor a spin. Any reason for supporting only Mongo ? Is it because libraries are yet to come out ? Edit: punctuation.
1) mongo's ability to have a live cursor that updates if the query returns new objects or changes within the objects currently being returned.
2) they have a minimongo which lives on the client. So code can do queries and not worry if the code is running client or server.
If meteor wasn't so tightly tied to mongo - I would hands down recommend it to a company doing node.js development.
Meteor is much easier than node to grok. ( no callback hell, no promises ) Meteor reads top to bottom the same as all the other languages out there. Node reads like a twisted spaghetti hairball that your cat vomited up.