Live data from Hacker News

Graphviz 7

gitlab.com

61–70 of 95 posts

Re: Graphviz 7

#61
post #18

Someone needs to make a multi-OS clone of omniGraffle. I paid €179 for omniGraffle, I’d pay for a multi-OS alternative.

I objected to how often I had to upgrade the version and pay for very minor fixes.

[deleted]

Re: Graphviz 7

#62
post #9

I liked GraphViz a lot, but eventually got frustrated with its layout algorithms and default look and feel. I would switch to Mermaid wholesale if it could render SVGs without requiring a browser engine.

I’ve personally settled on grapviz (a derivative actually, plantuml) being “good enough” for casual diagrams. Plantuml is built with the idea that it’s for quick and dirty communication, and I think graphviz translates well to this. It’s a nice way to put together a sequence diagram that just helps you understand control flow (and then never took at it again). I have to admit, I haven’t found a more formal programmat…

I also promote PlantUML for projects, specifically because:

1. It provides a convenient DSL targeting specific diagram use-cases that I actually want (generally sequence diagrams.)

2. The "source code" for the diagram is trivial to check in and diff with version-control, sometimes right along with the code it describes.

3. If the app/renderer is for some reason not available, the source is clear enough that you aren't completely lost.

I hadn't heard of Mermaid before this conversation, but it seems to hit some of the same notes.

Re: Graphviz 7

#64

Does anyone know of any DOT -> mermaidjs format converters? I was looking for one recently and was surprised not to find anything more robust than someone's quick search and replace script.

Does anyone want to look at porting the mermaid layout method back to Graphviz? It might be useful to people. I guess some friction would be around the kind of awkward way that Graphviz has to deal with objects that aren't strictly nodes, edges, or subgraphs.

Re: Graphviz 7

#66
post #65

Earlier quoted context omitted.

No idea why v7 is trending now. The big changes (moving to C99) are in v3 from 2022-02-26.

That's a lot of major versions in just a few months!

Looks like they consider any breaking change a major rev bump. And it looks like most releases since then have had at least one breaking change.

Re: Graphviz 7

#67

Earlier quoted context omitted.

Wild, seeing SemVer actually used properly.

The thing is, if you're writing software with a lot of breaking changes, SemVer doesn't make much sense, because you'll just quickly get to major version numbers in the hundreds.

Especially when the API surface area is as gigantic as graphviz's.

Still, it's great to see new maintainers with bold ideas.

Re: Graphviz 7

#68

Earlier quoted context omitted.

Wild, seeing SemVer actually used properly.

The thing is, if you're writing software with a lot of breaking changes, SemVer doesn't make much sense, because you'll just quickly get to major version numbers in the hundreds.

> The thing is, if you're writing software with a lot of breaking changes, SemVer doesn't make much sense, because you'll just quickly get to major version numbers in the hundreds

“The version number conveys whether there is a breaking change” seems more important than “the version number remains small”, so while the second half may be true, I don’t see how that supports the first half at all.

Post reply on HN