I had not seen that before, thanks!. The only thing that concerns me about glog is this statement: "The code in this repo is for export only and is not itself under development. Feature requests will be ignored."

I wonder what the differences between these two logging libraries are?

I know Tim wrote loggo specifically to solve some logging problems with Juju, which as the largest open source project in go, and as distributed system management tool puts a lot of pressure on getting good logging in place. But I'm less familiar with seelog's history, and the motivations behind it.