The first few graphs are impressive, it does a much tidier job. But the Go queue one is objectively worse - the other versions keep services and users grouped together, as well as a left-to-right flow. The TALA version makes it look more complicated than it is.
then after discovering it, I was too invested in my own project to switch -- the complexity in positioning nodes, routing edges to not draw over labels, taking into account nesting and rank dir gave me an appreciation for how hard these can be, and I kinda wanted my own version (plus other features)
The first few graphs are impressive, it does a much tidier job. But the Go queue one is objectively worse - the other versions keep services and users grouped together, as well as a left-to-right flow. The TALA version makes it look more complicated than it is.
Would integrating/implementing this into graphviz be a good move or mixing wrong things?
before discovering d2, I wrote / vibe coded my own diagram generator: https://azriel.im/disposition
then after discovering it, I was too invested in my own project to switch -- the complexity in positioning nodes, routing edges to not draw over labels, taking into account nesting and rank dir gave me an appreciation for how hard these can be, and I kinda wanted my own version (plus other features)
I just started diagramming with d2- I'll have to try this one out!
Thanks for that. What do you think are the key heuristics / concepts that made it standout or be more appropriate for architecture diagrams?
Related:
D2 Is Non-Profit
https://news.ycombinator.com/item?id=49589768