13 points | by aqula 2 hours ago ago
7 comments
I love this! It's relatively simplistic and would be a really fun tool to use during lectures.
How does it decide which call graphs to include? In a typical project there can be many and these graphs seem to be a small subset.
It identifies telemetry, accessors, and other trivial code and strips them out of the graph. The idea is to retain architecturally relevant parts of the code.
I wish something like this could trace also data flow in a program.
Something I do have in mind. Do you have an idea of the kind of UX you'd like to see?
Only naïve ones I'm afraid, such as a heap view.
How u make this??
I love this! It's relatively simplistic and would be a really fun tool to use during lectures.
How does it decide which call graphs to include? In a typical project there can be many and these graphs seem to be a small subset.
It identifies telemetry, accessors, and other trivial code and strips them out of the graph. The idea is to retain architecturally relevant parts of the code.
I wish something like this could trace also data flow in a program.
Something I do have in mind. Do you have an idea of the kind of UX you'd like to see?
Only naïve ones I'm afraid, such as a heap view.
How u make this??