Graph Mining Library
31–40 of 113 posts
Re: Graph Mining Library
#32Interesting fact: the first commit is 2 years old and is entitled "Boilerplate for new Google open source project". Either they rewrite git history or it took about 2 years to get approval on making this repo public.
So probably they just started the project two years ago, had aspiration to open source, and finally just did now. Some teams might publish earlier, some like to wait until it's had enough internal usage to prove it out.
Re: Graph Mining Library
#33Re: Graph Mining Library
#34This is a big deal, I think. I'm guessing it's not widely used internally anymore if they are open sourcing it. What is used instead?
Re: Graph Mining Library
#35Earlier quoted context omitted.
As merely two examples, both gRPC and Kubernetes are important to Google, and yet Google opened sourced them. "No longer used" is not the criteria Google uses to make their software OSS. FYI, I work at Google.
Google Wave is the only counterexample I can think of, where it was "we're deprecating this project, but releasing it as open source".
Open source at Google generally takes the form of libraries rather than products. Often, that's something that an individual engineer is working on, and it's easier to open source than get the copyright reassigned (since Google by default owns any code you write). There are also libraries that are open sourced for business reasons - e.g. SDKs. You can tell the difference, because most individually-driven libraries contain the copy "Not an official Google product" in the README.
Re: Graph Mining Library
#36Re: Graph Mining Library
#37Re: Graph Mining Library
#38Is "Graph Mining" so ubiquitous that people know what this is all about?
Re: Graph Mining Library
#39No idea where is the hype coming from, who is actually upvoting this? 0 Docs, 0 examples, 0 explanation of how is it useful. Is "Graph Mining" so ubiquitous that people know what this is all about?