I think seeing what atoms you have in app is useful because this is what your app is about, full picture. Guess there will single (usually) atom with app state, several with component local state (think React app), then atoms which bridges external state (browser history) — could be useful to have an API to tag atoms somehow (component local, app, history.
Then see what changes when you interact with the app.
Also seeing what reactors are active (could be also made with tagging). Like what components are subscribed to what and when they are re-rendered.
.derive()method allows to deref other derivable? Will they be tracked then? 2) less API surface 3) consistent pattern for accessing derivable value
d.derive(v => ...)
deriveInWorker<T, R>(source: Derivation<T>, derive: (value: T) => R): Derivation<?R>
nullif result isn't ready yet
sourceand submit task to a worker and put result eventually into another atom I return from
deriveInWorker. Then (important) I want not to do any work if there's no reactions active on the derivation I return.