This seems mostly exercise in Haskell programming, and not really related to actual things that people look for in the build system. For example, paper talks a

This seems mostly exercise in Haskell programming, and not really related to actual things that people look for in the build system. For example, paper talks a great deal about schedulers, but those are very minute implementation details. If bazel gets "suspending" scheduler instead of "restarting" one, this is a super major change in the paper's eyes, but no user is likely to notice (other than "hey it works 2% faster now, cool!"). Moreover, the paper's scheduler abstraction is too limited - there are a whole bunch of schedulers which are non-representative in it, for example imagine a scheduler which is aware of memory and CPU usage, and schedules the tasks to avoid out-of-memory condition (like recent bazel). The division on "cloud" vs "non-cloud" systems is also pretty weird... ok, bazel has cloud caching built-in but make requires external "ccache", but the resulting behaviors are pretty similar.