Introducing Abseil, a new common libraries project

Re:Introducing Abseil, a new common libraries project by jzelinskie on Thursday September 28, 2017 @01:16AM (#15354823)

Thanks for the response. Are things moving into third party or are new projects being created in third party and maintained alongside the originals?

I and probably many others are more likely to be willing to depend on a library if I know Google internals directly depend on the maintenance of said library.

[ Parent | on HN ]

Re:Introducing Abseil, a new common libraries project by yegle on Thursday September 28, 2017 @01:55AM (#15354967)

Likely no one would answer this question considering the info is confidential. I think the best way to understand how Google uses a monorepo is this doc [0].

Disclaimer: yes I work for Google but my work is not related to Abseil team.

[0]: https://cacm.acm.org/magazines/2016/7/204032-why-google-stor...

[ Parent | on HN ]

Re:Introducing Abseil, a new common libraries project by joshuamorton on Thursday September 28, 2017 @01:57AM (#15354979)

Parroting this comment (that is probably confidential), the abseil website does include this statement:

>The libraries we are releasing come with a pedigree: many years of experience using these APIs in Google’s production environments. We’ve seen what works and what doesn’t, what designs lead to bugs, performance problems, and misuse. What you see here is what we found to be a good balance between simplicity and meeting the needs of production use and an ever-evolving codebase. [1]

Also a googler who has nothing to do with abseil.

[1]: https://abseil.io/

[ Parent | on HN ]