Most businesses aren't based on discovery of anything other than customers for a transaction they already have. This comes up with graph based recommendation engines, which are essentially a surveillance/marketing product based on preferences. Surveillance seems to be their default use case, with open ended scientific research a close second. Imo, they're useful for one-off pattern discovery, and they're most valuable for finding single or a few exceptions and outliers in normalized data, and you need to be in an environment where there are asymmetric returns on finding those. They're really compelling but oddly unpopular. They yield the fastest path through complex problems, and I use them to do in a couple of hours what typically would take client staff months. I use graphs in security and privacy quite a bit, and even built the tech for a hopeful security platform using a graph back end. Graphviz is an amazing tool, it has just suffered from being cloistered to technologists whose jobs aren't to solve the kinds of problems it is specifically adapted for. No doubt there are more details if anyone can remember them. In the worst case, this has to be debugged for all the drivers in Maybe it wore away as waves of open source development washed over it, along with static tables for a bunch of "standard" PS fonts. There is no question there was once upon time explicit code to try to cope with this problem, at least in the native PSgen, but I can't find it now. Perhaps the loop stops sometimes on the wrong side of the boundary? Anyway, it's equally possible that when the endpoint coord is handed off to a lower level driver, the arrowhead mitering is wrong. If this isn't right, maybe somebody can figure out why. (That, and text with slightly-off baselines.) "Very poor" seems harsh, but, yes, it hurts us, too. credit card processing, because in the end it's more profitable to solve big end customer problems. It's surprising the conventional relational database products don't pay much attention to this opportunity, but they have gone vertical, e.g. It's not hard to understand why that is valuable, but Neo4J sell it as being "efficient for linked structures" (relational databases don't have foreign keys and indices) and "intuitive" (have you ever tried to read the code for graph matching in Cymbal? I rest my case.) They have investments of hundreds of millions? Worth billions? They contributed something valuable to the tech economy. It does something important, mainly, rationalize the mess of graph representations and algorithms. Anyway, gvpr is a modest attempt at a sort of graph query language. It would take more resources, or intensity, than what we had. When we started Graphviz, we vaguely sensed the potential for graph databases or environments, like neo4j, but we didn't work much in that area.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |