I like the idea of being able to express diagrams with a "text notation" because it makes it really easy to use these diagrams in documentation or documents wit

I like the idea of being able to express diagrams with a "text notation" because it makes it really easy to use these diagrams in documentation or documents with the plus of being able to store then (with code?) in a source control environment. But this imperative approach tights everything together with the language and then the graph engine is not just a tool, is a lib that you have to incorporate in your system. Based on that I like the declarative approach used by js-sequence-diagrams [1] and flowchart.js [2] much more, it gives you the freedom to use the syntax instead of the code... js-sequence-diagrams goes even further and creates a svg that has the source it used to generate the image embedded in the markup, so you can aways look the image and go back to add/remove details from your diagram, which is pretty awesome for using in a constantly evolving documentation. [1] https://github.com/bramp/js-sequence-diagrams https://github.com/bramp/js-sequence-diagrams [2] http://adrai.github.io/flowchart.js/ http://adrai.github.io/flowchart.js/