@martinklepsch: Thanks. That's interesting to know. I think I tried Reagent 0.6 when it first came out, had some problem or other, and backed away, thinking to myself that discretion was the better part of valor - very wimpy of me, I know. So knowing that others have succeed is encouraging.

@nidu we don't completely avoid them, but they're not very common, as each view component is only responsible for one 'thing' so we're not switching between different logical datasets. I see dynamic subscriptions being good for subscriptions that are parametrised over one logical thing. Hope that helps

@danielcompton: thanks, that makes sence

Trying to understand re-frame: wondering what the relation is between reagent/track and reframe's subscription. Seems like they both try to memoize, possibly delay expensive lookups and produce a derefable state, am I right?

Also is it common to use so-called container components with re-frame? Here's some info: https://medium.com/@learnreact/container-components-c0e67432e005#.t9nardmby

Regarding container components, the answer is yes, they are useful: https://github.com/Day8/re-frame/wiki/Using-Stateful-JS-Components

The purpose of subscriptions is to hide, from Components, the source of data.

But, in the process, to supply a reactive source of data. One which provides a stream of data.

mikethompson: so, not having to pass around an atom is the big advantage over r/track?

I was annoyed to see r/track added to Reagent. It is just going to confuse everyone, I said. I grumpily undertook to not spend my life explaining.

Perhaps other will

mikethompson: hmm I see...