I’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... - https://d2lang.com/tour/api/
Vizdom: Diagrams as Code
31–40 of 68 posts
Re: Vizdom: Diagrams as Code
#32Earlier quoted context omitted.
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 wh…
I free to redistribute the WASM blob to my end users? The blob itself is Apache? I know binaries can be under Apache without being source available but I just want o make sure I understand correctly
Re: Vizdom: Diagrams as Code
#33Earlier quoted context omitted.
I wrote some functionality to parse DOT to feed it into the layout engine before I got everything working. It was a great way to validate more complex graphs with a DSL that is already prevalent. So for now it’s only present in the webapp. DOT parsing isn’t part of the npm package, but I’m not totally opposed to include it! It may add 1-2Mb more to the wasm bundle.
> So for now it’s only present in the webapp. Just so you know, I find this terribly confusing. You see the homepage with your code, then you think "oh, I'll try this editor here..." and then it turns out it's Dot? All examples are written in Dot? Why? Didn't it say "no DSLs"? Didn't it show some TypeScript in the homepage? It can very easily make people get the wrong idea about what your project is.
Edit: It seems to have almost 100% feature overlap with graphviz, but it is a paid SaaS? I don't get it...
Edit 2: This has to be a troll post. "Up to 3 graphs" for free --are you kidding me? I can run `dot` a million times in a second for free
Re: Vizdom: Diagrams as Code
#34I also wanted to give a shoutout to Greg who built the amazing Leptos rust framework that powers everything. Read more here: https://leptos.dev/
Re: Vizdom: Diagrams as Code
#35Re: Vizdom: Diagrams as Code
#36Earlier quoted context omitted.
I wrote some functionality to parse DOT to feed it into the layout engine before I got everything working. It was a great way to validate more complex graphs with a DSL that is already prevalent. So for now it’s only present in the webapp. DOT parsing isn’t part of the npm package, but I’m not totally opposed to include it! It may add 1-2Mb more to the wasm bundle.
> So for now it’s only present in the webapp. Just so you know, I find this terribly confusing. You see the homepage with your code, then you think "oh, I'll try this editor here..." and then it turns out it's Dot? All examples are written in Dot? Why? Didn't it say "no DSLs"? Didn't it show some TypeScript in the homepage? It can very easily make people get the wrong idea about what your project is.
Really good feedback and I’m being serious. Wish I saw that earlier.
Re: Vizdom: Diagrams as Code
#37Earlier quoted context omitted.
> So for now it’s only present in the webapp. Just so you know, I find this terribly confusing. You see the homepage with your code, then you think "oh, I'll try this editor here..." and then it turns out it's Dot? All examples are written in Dot? Why? Didn't it say "no DSLs"? Didn't it show some TypeScript in the homepage? It can very easily make people get the wrong idea about what your project is.
TBBQF I have no idea what the value proposition of this project is actually supposed to be. Edit: It seems to have almost 100% feature overlap with graphviz, but it is a paid SaaS? I don't get it... Edit 2: This has to be a troll post. "Up to 3 graphs" for free --are you kidding me? I can run `dot` a million times in a second for free
You can create and render as many graphs as you like with the package offline - only the real-time sync is limited.
Re: Vizdom: Diagrams as Code
#38Earlier quoted context omitted.
"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 a bit of a pain point." Hi, creator of Ilograph[0] here. I agree with this if the DSL doesn't provide an IDE with autocomplete and instant-rendering (which I think applies to the technologies you mentioned). With auto-complete and…
Neat product! I like the interactivity. For me (and my narrow use-case), I just couldn’t find a simple tool to sync my graph to somewhere that I could view it easily - especially after I’ve instrumented my application and deployed to the cloud.
Re: Vizdom: Diagrams as Code
#39Re: Vizdom: Diagrams as Code
#40Earlier quoted context omitted.
TBBQF I have no idea what the value proposition of this project is actually supposed to be. Edit: It seems to have almost 100% feature overlap with graphviz, but it is a paid SaaS? I don't get it... Edit 2: This has to be a troll post. "Up to 3 graphs" for free --are you kidding me? I can run `dot` a million times in a second for free
Yeah I’ll admit, that isn’t clear. I used DOT to test it a while back and opened that up for folks who also wanted to mess with DOT, but that isn’t the value prop today. You can create and render as many graphs as you like with the package offline - only the real-time sync is limited.
Why wouldn't I just use graphviz then?