This time last year, I was deep into writing Gradle plugins at work. Gradle's entire architecture is the best argument I have ever seen for why you should neve

This time last year, I was deep into writing Gradle plugins at work. Gradle's entire architecture is the best argument I have ever seen for why you should never use a big blob of shared mutable state when all you really needed to do was pass discrete values up and down the call stack. Compare with Bazel. I appreciate why people bounce off of many of its strictures. But when you just look at the architecture and what it takes to develop for it, it's amazing how much easier it is to grok, while achieving a similar level of flexibility.