Phloem
Phloem is a Git history visualization tool developed by Anthony Fu. It adopts the metaphor of slime mold growth, revealing the evolutionary structure of a repository by generating commits incrementally along commit edges rather than laying them out all at once.
Timeline (last 90 days)
Developer Anthony Fu made a Git history visualization tool called Phloem, replacing the traditional spread-out DAG layout with a slime mold growth metaphor.
The inspiration for Phloem first appeared in a Hacker News discussion thread with post ID 50054465.
Phloem does not use a layout algorithm that solves the complete commit DAG all at once, but instead progressively generates the graph along the connections between commits.
Phloem is an exploratory tool and cannot replace git log, git bisect or blame.
Phloem is suitable for those encountering a large open-source repository for the first time who want to quickly sense how the project structure evolved, for code archaeology to trace the origin of modules, and for creators who use repository history as visualization material.
Phloem is not suitable for daily development that requires precisely listing the diff of a certain commit, for compliance scenarios that require strict auditing of commit order, and for team processes that rely on fixed graphical semantics.
The slime mold-style layout makes paths appear as organic curves rather than straight lines, which is a burden in high-precision coordinate scenarios.
Phloem externalizes the branch-probe-reinforce-shrink process of Git history into a visible form, with line thickness and contraction corresponding to a true projection of the development process.
All Facts (8)
Phloem externalizes the branch-probe-reinforce-shrink process of Git history into a visible form, with line thickness and contraction corresponding to a true projection of the development process.
50%UnverifiedDeveloper Anthony Fu made a Git history visualization tool called Phloem, replacing the traditional spread-out DAG layout with a slime mold growth metaphor.
50%UnverifiedPhloem does not use a layout algorithm that solves the complete commit DAG all at once, but instead progressively generates the graph along the connections between commits.
50%UnverifiedPhloem is an exploratory tool and cannot replace git log, git bisect or blame.
50%UnverifiedPhloem is suitable for those encountering a large open-source repository for the first time who want to quickly sense how the project structure evolved, for code archaeology to trace the origin of modules, and for creators who use repository history as visualization material.
50%UnverifiedPhloem is not suitable for daily development that requires precisely listing the diff of a certain commit, for compliance scenarios that require strict auditing of commit order, and for team processes that rely on fixed graphical semantics.
50%UnverifiedThe slime mold-style layout makes paths appear as organic curves rather than straight lines, which is a burden in high-precision coordinate scenarios.
50%UnverifiedThe inspiration for Phloem first appeared in a Hacker News discussion thread with post ID 50054465.
50%