Live data from Hacker News

Vizdom: Diagrams as Code

vizdom.dev

61–68 of 68 posts

Re: Vizdom: Diagrams as Code

#61

for new register: password require at least 16 characters and contain: an uppercase letter, a lowercase letter, a number, and a symbol. Its too complex for even Chrome built-in secure password generator to come up with, let alone a human.

Then use a different password manager. Bitwarden has no problems with that. PaSsw0rd123$56_!

Re: Vizdom: Diagrams as Code

#63

Other than Graphviz (can try one of its other visual editors[3]), other generic text to diagram tools/langs in this space are Pikchr[1] and D2[2]. UPDATE: Just realized that Vizdom here is not a new language, but a Graphviz editor. [1]: https://pikchr.org/home/pikchrshow [2]: https://play.d2lang.com/ [3]: http://magjac.com/graphviz-visual-editor/

[dead]

Re: Vizdom: Diagrams as Code

#64
post #59

Doing a layout algorithm is very difficult, and the DOT code made me curious, so I decompiled the wasm and looked around a bit. I see this appears to use or build on Dagre ( https://github.com/dagrejs/dagre/wiki ), though I've seen no citation of that work. What's up with that? How much of this is original work vs pulling together tools in a new way or improving their API?

Thank you for pointing this out - it was an error. I actually even forgot to credit the dependencies the binary was built from!

However, that is now resolved. The latest distribution has license mentions for:

- Dagrejs

- NotoSans Font

- *Others (an html file generated via `cargo about` that list all deps used in the final dist)

That being said, I did want to point out that I did take significant influence from Dagrejs which is why you see that the layouts produced look very similar - it is a rough translation into rust. There are changes to some DFS traversals, other optimizations that are rust-specific, and countless bug fixes. I actually spent a lot of time attempting to reproduce the layouts that Dagre generates, but there are some examples that do not produce the same results. At this point, I think it is close enough and would rather spend time writing a new set of algos for better edge crossing minimization and cluster support.

Re: Vizdom: Diagrams as Code

#65
post #6

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.

Sounds like an interesting app. But I just wanted to comment that I don't need an account to use draw.io and I can download an xml of the diagram just fine from them. I noticed you didn't mention them in your comment, so perhaps they are not a competition?

Yeah not really competition as I see it. If you create graphs rarely or need to craft one manually then there are better tools out there.

Maybe my landing page is terrible, but you don’t need an account to download the npm package and start doing things locally.

That being said, I’m more interested in helping individuals who want to programmatically generate graphs - hundred+ updates to them per day, similar to how an APM/telemetry libs work. You instrument once and get the benefits of a real-time graph.

Re: Vizdom: Diagrams as Code

#66
post #64
post #59

Doing a layout algorithm is very difficult, and the DOT code made me curious, so I decompiled the wasm and looked around a bit. I see this appears to use or build on Dagre ( https://github.com/dagrejs/dagre/wiki ), though I've seen no citation of that work. What's up with that? How much of this is original work vs pulling together tools in a new way or improving their API?

Thank you for pointing this out - it was an error. I actually even forgot to credit the dependencies the binary was built from! However, that is now resolved. The latest distribution has license mentions for: - Dagrejs - NotoSans Font - *Others (an html file generated via `cargo about` that list all deps used in the final dist) That being said, I did want to point out that I did take significant influence from Dagrej…

Cool, thanks - it makes sense to build on or be (directly) inspired by these other projects.

Re: Vizdom: Diagrams as Code

#67
post #57
post #53

Earlier quoted context omitted.

Also, if you're using python today, take a look at https://diagrams.mingrammer.com/ It's pretty good - uses Graphviz under the hood, but supports many cloud icons/logos. Not completely sure if it allows you to provide any icon, but it wouldn't surprise me.

Yes, that's my ideal, but I use TS :)

Cool I’ll put this on my roadmap

Re: Vizdom: Diagrams as Code

#68
post #8
post #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.

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/ren…

Ah ok thanks for clarifying!
Post reply on HN