"Tracker.autorun" vs "new Meteor.Computation"?

core
1
  • Since Tracker.autorun creates a new computation, is it not cleaner to call new Meteor.Computation ?
  • Do we need to claim another global variable for Tracker, or can users simply access it via Meteor ?
  • Can we have a concept of a currentValue, and make the return value meaningful, not just trigger side-effects on reactive changes ?

See an example project here: https://atmospherejs.com/deanius/meteor-computation

What are your thoughts ?

2

Just a heads up - the return value of Tracker.autorun is already the computation: http://docs.meteor.com/#/full/tracker_autorun

1 Like