I'm not at all clear why this blog post is touted as evidence that the tiny modules approach is correct. I think it might be all the people after it congratulat

I'm not at all clear why this blog post is touted as evidence that the tiny modules approach is correct. I think it might be all the people after it congratulating him. "It's all about containing complexity." - this completely ignores the complexity of maintaining dependencies. The more dependencies I have the more complicated my project is to maintain. Dependencies are pieces of software managed by separate entities. They have bugs and need updates. It's hard to keep up to date. When I update a piece of software I read the CHANGELOG, how am I expected to read the CHANGELOG for 1,000 packages? Depending on a bigger package (handled by the same entities, who write one changelog, in the same form) is more straight forward. I'm not saying this is wrong - but there's a balance here, and you must not ignore the complexity of increasing your number of dependencies. It does make things harder.