What is also interesting is that the appenwar implementation has now support for serializing logs in parallel builds: https://apenwarr.ca./log/20181106 https:/

What is also interesting is that the appenwar implementation has now support for serializing logs in parallel builds: https://apenwarr.ca./log/20181106 https://apenwarr.ca./log/20181106 The linked documentation does a good job why redo is a very, very interesting (and for the complexity of the task, stunningly simple) approach to a build system. I find the approach to support parallel builds quite enlightening, and I also like a lot the property that it is language-agnostic, which is very helpful for larger projects, but also makes it easier to include special tools in C/C++ projects. There are also some shortcomings of the design and some implementations of redo which are discussed here: https://jdebp.eu/FGA/introduction-to-redo.html https://jdebp.eu/FGA/introduction-to-redo.html