[Leftium]

I edited my first comment, but perhaps this deserves its own comment:

https://docs.meteor.com/api/tracker.html

> Meteor has a simple dependency tracking system which allows it to automatically rerun templates and other computations whenever Session variables, database queries, and other data sources change.

> Unlike most other systems, you don’t have to manually declare these dependencies — it “just works”. The mechanism is simple and efficient. When you call a function that supports reactive updates (such as a database query), it automatically saves the current Computation object, if any (representing, for example, the current template being rendered). Later, when the data changes, the function can “invalidate” the Computation, causing it to rerun (rerendering the template).

[lolc]

I enjoyed using Meteor. It is magic at first, and still rather elegant when you get into advanced stuff. The main downside for me was that it uses Mongodb. We had to denormalize heavily to get it working acceptably fast. There was talk about Postgres support, so maybe that is solved.