There’s a good chance you’re absolutely correct about the scalability. Then again, not all solutions need to work at all scales to have value.

I found out about google/wire — a compile-time dependency manager — after writing this article. The project even got it’s own announment and kick off through golang.org.

I have no doubt a lot of thought went into it’s design. However, I did find it hard to understand the initial tutorial and it also felt very “un-Go” to me. I have not used it yet though.

In theory, libraries that have proven to provide benefit to projects should bubble up and continue to be maintained. So all I can do is leave it up the democracy of open-source to let me know if this approach is a yay or a nay for Go. :)