Vizdom: Diagrams as Code
vizdom.dev
Vizdom: Diagrams as Code
1–10 of 68 posts
Re: Vizdom: Diagrams as Code
#2How does this compare to D2 and Mermaid?
Re: Vizdom: Diagrams as Code
#3How does this compare to D2 and Mermaid?
One thing is they're open source.
> the Rust WebAssembly binary included in this library is closed-source.
Re: Vizdom: Diagrams as Code
#4"Diagrams as Code" has been around a long time (e.g. DOT), not sure what this is really bringing as an improvement, especially as seems to require an account (at least it does when I click "get started" and, as someone else points out, is closed source.
Re: Vizdom: Diagrams as Code
#5> Please note that while Vizdom is freely available for use under the Apache License 2.0, the Rust WebAssembly binary included in this library is closed-source.
So, the examples are open source (and the README). https://github.com/vizdom-dev/vizdom
Re: Vizdom: Diagrams as Code
#6I’m the author, I just got tired of using a DSL and wanted a way to programmatically write/build a graph and quickly see the rendering.
DLS-based diagramming tools like Terrastruct, mermaid, or graphviz definitely have their perks and are very well established for manual graph curation. But I found the lack of programmatic tooling (except terrastruct) a bit of a pain point.
Re: Vizdom: Diagrams as Code
#7I’m the author, I just got tired of using a DSL and wanted a way to programmatically write/build a graph and quickly see the rendering. DLS-based diagramming tools like Terrastruct, mermaid, or graphviz definitely have their perks and are very well established for manual graph curation. But I found the lack of programmatic tooling (except terrastruct) a bit of a pain point.
Can you explain the licensing? There’s several comments noting some closed source WASM blob.
Re: Vizdom: Diagrams as Code
#8"Diagrams as Code" has been around a long time (e.g. DOT), not sure what this is really bringing as an improvement, especially as seems to require an account (at least it does when I click "get started" and, as someone else points out, is closed source.
The npm package is free to use, but closed source until I have bandwidth.
To be clear, you don’t need an account to use the npm package which has all of the functionality to perform layout and rendering. An account is only needed if you want to sync the graph and have a web page to view renderings. This is useful if you’ve instrumented a long lived application with Vizdom, but don’t want to produce a local layout/rendered image because you can’t really “view” it if the service is running in the cloud.
Re: Vizdom: Diagrams as Code
#9I’m the author, I just got tired of using a DSL and wanted a way to programmatically write/build a graph and quickly see the rendering. DLS-based diagramming tools like Terrastruct, mermaid, or graphviz definitely have their perks and are very well established for manual graph curation. But I found the lack of programmatic tooling (except terrastruct) a bit of a pain point.
Congrats on the launch! I'm the author of D2 (Terrastruct). I won't comment on comparisons you want to make as it's your launch, but just to clarify, we do have a programmatic API:
- https://terrastruct.com/blog/post/generate-diagrams-programm...
Re: Vizdom: Diagrams as Code
#10I’m the author, I just got tired of using a DSL and wanted a way to programmatically write/build a graph and quickly see the rendering. DLS-based diagramming tools like Terrastruct, mermaid, or graphviz definitely have their perks and are very well established for manual graph curation. But I found the lack of programmatic tooling (except terrastruct) a bit of a pain point.
Can you explain the licensing? There’s several comments noting some closed source WASM blob.
Sure! It’s Apache 2.0 licensed, but yes the binary wasm blob is what does all the work and is closed source for the time being.
It’s about 25k lines of rust code compiled to do the following:
- Layout/position a directed graph
- Compute a bounding box for text labels and produce font glyphs for the rendering engine
- Generate an SVG
- Optionally, sync to a Vizdom account
Fun fact, the majority of that wasm blob is what is powering the web application itself. You can see it in action using the editor view/diff on the site.