Live data from Hacker News

Graphviz 7

gitlab.com

51–60 of 95 posts

Re: Graphviz 7

#51

Earlier quoted context omitted.

Shouldn't the extension be .dot?

.gz is already used by gzip[1]. This wiki[2] says it is .gv . I've always used .dot so I don't know what to use anymore. edit: according to this[3] discussion , Microsoft uses .dot. I then found this wiki[4] page that supports the claim. dot is used by Microsoft Word document template files. I will switch to .gv [1] https://en.wikipedia.org/wiki/Gzip [2] https://en.wikipedia.org/wiki/DOT_(graph_description_languag...…

I've used .dot in the past and stumbled upon issues with git related tools (I believe git diff) interpreting the .dot file as a word related file. I'm using .gv now.

Re: Graphviz 7

#52

One of the better graph visualization tools! Which tool do you people use most often for graph visualization? I kind of linger between networkx, Gephi, graphviz and d3.

I often use https://github.com/Rubjerg/Graphviz.NetWrapper to export the graphviz layout as json and then use d3 for rendering :)

Re: Graphviz 7

#53
post #9

I liked GraphViz a lot, but eventually got frustrated with its layout algorithms and default look and feel. I would switch to Mermaid wholesale if it could render SVGs without requiring a browser engine.

Sketchviz looks a bit nicer, but also 'sketchy' https://sketchviz.com/new Regarding mermaid, see my misplaced comment one level deeper. I'd think that with node.js it can export to svg.

Re: Graphviz 7

#55
Graphviz is one of those things I wish I had found much much earlier in my career. It makes throwing together a little one off tools to chart data relationships effortless.

Re: Graphviz 7

#56
post #18

Someone needs to make a multi-OS clone of omniGraffle. I paid €179 for omniGraffle, I’d pay for a multi-OS alternative.

I objected to how often I had to upgrade the version and pay for very minor fixes.

I bought it 5 years ago and haven't given them a dime since, and got a lot of new feature since (scripting!). I'd love to have more library, but that's another issue :)

Re: Graphviz 7

#57
Out of curiosity, has anyone settled on a method for storing and surfacing metadata about a node?

Example: a server has an IP address, dns entries, a description, and some other fields, and it connects to other servers. Is all of that meta information in a JSON object in the key-value area of the node in the .dot file?

Re: Graphviz 7

#58
post #15

This is more for diagramming small graphs. If you are trying to render large networks, there are better alternatives. For OSS graph visualization libraries, check out: - Sigma.js - Vis.js For commercial options: - Ogma (disclosure: my company builds that one) - KeyLines

js.cytoscape.org is pretty cool too for fast layout of large nets

Re: Graphviz 7

#59
post #51

Earlier quoted context omitted.

.gz is already used by gzip[1]. This wiki[2] says it is .gv . I've always used .dot so I don't know what to use anymore. edit: according to this[3] discussion , Microsoft uses .dot. I then found this wiki[4] page that supports the claim. dot is used by Microsoft Word document template files. I will switch to .gv [1] https://en.wikipedia.org/wiki/Gzip [2] https://en.wikipedia.org/wiki/DOT_(graph_description_languag...…

I've used .dot in the past and stumbled upon issues with git related tools (I believe git diff) interpreting the .dot file as a word related file. I'm using .gv now.

Oh right, back in the day .dot was a template file.

.doc = document, .dot = document template.

Re: Graphviz 7

#60

I use Graphviz dot syntax to configure entire cloud computing environments in the order they must be built. This is pipelines as code and infrastructure as code It's very powerful! Not every organisation can bring up an entire environment with one command of documentation their infrastructure with Graphviz. Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, J…

I’ve kind of considered something similar to this approach but ended up using a graphdb to keep dependencies instead.

Using a db gives you a better way of modifying meta data in batches which might be required at scale. It also makes it possible for tooling to query stuff quickly and do operations such as setting consul intentions, register something in an api gateway or other surrounding config tasks.

The pipelines we built checked out complete subgraphs from an api and generated json that referenced versioned TF modules and committed these to a service repo.

Thought about open-sourcing for a long time but never could get the go from legal. :(

This is very cool though!

Post reply on HN