First, thanks again for the amazing work on yet another amazing tool!
Just a suggestion; if Mill is really basing many of its principles on CBT,
I think some credit should be given in the docs at e.g.
Not just for giving some credit where credit is due (though that never
hurts), but also to outline some of the ideas described above.
Additionally, it would be great to be as unbiased as possible: are there
cases where someone might prefer CBT to Mill, and if so, why. This last one
may not need to go directly in the docs, but as someone who has been
enthusiastic about CBT for some time, I’d really like to know. Based on the
discussion above, I can’t think of anything definite, since it sounds like
the rigidity imposed by the task graph may be relatively easy to sidestep
(please correct me if I’m wrong). However, one point is just that a task
graph may behave in undesired ways (or at least, non-obvious ways): you
can’t see what is going on, as easily as you could if it were coded up in
simple Scala. Again, I haven’t used either tool extensively, and Mill not
at all as yet.