91–100 of 113 posts
Graph algorithms cry out for some standardization. Think blas and lapack.
Consider: https://graphblas.org
some examples would be super helpful!
Whew. Lots of complaints from people who probably will never need to use this code. If you need docs just read the .h files, they have extensive comments. I’m sure they’ll add them or maybe, just maybe, you could write some to contribute. This would have made some of my previous work much easier, it’s really nice to see google open source this.
How is this usable. I see no documentation. There is a docs folder but all it contains is a code of conduct.
I might be (very) far behind the times, but does this have any relationship with Pregel?
Or do(better?) frameworks for the same function as this code already exist(maybe networkx?)?
How is this usable. I see no documentation. There is a docs folder but all it contains is a code of conduct.
I'm not trying to be snarky but have you considered reading the code? Like I'll be honest I can't remember the last time I looked at docs at all instead of reading the code itself.
$ cat $(find . -type f | grep -vE LICENSE\|README\|BUILD\|bazel\|git\|docs) | sort -u | wc -l
8360 unique lines scattered across more than 100 files. Good luck deciphering that in a single day!
By the way, the first issue in the repo is a "Request for a more verbose README", which I agree with.
Earlier quoted context omitted.
I'm not trying to be snarky but have you considered reading the code? Like I'll be honest I can't remember the last time I looked at docs at all instead of reading the code itself.
Are you for real? I'm also not trying to be snarky but... $ cat $(find . -type f | grep -vE LICENSE\|README\|BUILD\|bazel\|git\|docs) | sort -u | wc -l 8360 unique lines scattered across more than 100 files. Good luck deciphering that in a single day! By the way, the first issue in the repo is a "Request for a more verbose README", which I agree with.
so as i see it you have like three options if you are unhappy with that:
1. close the tab
2. dig into the impl and learn as you go
3. do 2 but also write docs
i just really believe i've covered literally all the cases that any reasonable (not whiney, not entitled) person would concede.
> the first issue in the repo is a "Request for a more verbose README", which I agree with.
posted today - do you think it might have something to do with this post we find ourselves convening on? i.e. no one was so bothered about a lack of docs until now?
edit:
i forgot actually something else you could do: email the author and ask nicely for some tips.
Earlier quoted context omitted.
> a universal approach to data, see RDF and SPARQL and numerous pretenders. For that matter, think of a C program where the master data structure is a graph of pointers. A graph of typed pointers. As you likely know, the basic element of RDF is not “ foo has a relationship with bar ”, but “ foo has a relationship with bar of type baz ”. Also, the types themselves can be part of relationships as in “ baz has a relatio…
Funny, the core table of salesforce.com is triples but they got a patent circa 2000 on a system that builds indexes and materializes views based on query profiling so the performance is good (w/ gold plated hardware). That patent is one reason why graph databases sucked for a long time. Now the Lotus notes patents have been long expired so I’d like to see some graph database based products that can do what Notes did…