communities VS graphtage

I made a tool for plotting graphs with community structure. You can check it out here.

A few people are asking what this is a visualization of. OP's graphs look very similar to an example of the Louvain Method shown in the library's documentation. The Louvain Method is a community detection algorithm used on network graphs. It works by iteratively optimizing modularity of the graph. Modularity is a measure of the density of the number of edges (lines between nodes) that fall within a given group/cluster compared to what would be expected from a random distribution of edges throughout the graph.

I made this visualization with: https://github.com/shobrook/communities

I'm not familiar with Pijul, and haven't finished watching this presentation, but IME the problems with modern version control tools is that they still rely on comparing lines of plain text, something we've been doing for decades. Merge conflicts are an issue because our tools are agnostic about the actual content they're tracking.

Instead, the tools should be smarter and work on the level of functions, classes, packages, sentences, paragraphs, or whatever primitive makes sense for the project and file that is being changed. In the case of code bases, they need to be aware of the language and the AST of the program. For binary files, they need to be aware of the file format and its binary structure. This would allow them to show actually meaningful diffs, and minimize the chances of conflicts, and of producing a corrupt file after an automatic merge.

There has been some research in this area, and there are a few semantic diffing tools[1,2,3], but I'm not aware of this being widely used in any VCS.

Nowadays, with all the machine learning advances, the ideal VCS should also use ML to understand the change at a deeper level, and maybe even suggest improvements. If AI can write code for me, it could surely understand what I'm trying to do, and help me so that version control is entirely hands-free, instead of having to fight with it, and be constantly aware of it, as I have to do now.

I just finished watching the presentation, and Pijul seems like an iterative improvement over Git. Nothing jumped out at me like a killer feature that would make me want to give it a try. It might be because the author focuses too much on technical details, instead of taking a step back and rethinking what a modern VCS tool should look like today.

[1]: https://semanticdiff.com/

[2]: https://github.com/trailofbits/graphtage

[3]: https://github.com/GumTreeDiff/gumtree

Vielleicht mal https://github.com/trailofbits/graphtage abchecken

Graphtage: A semantic diff utility for JSON, HTML, YAML, CSV, etc\ (42 comments)