Visualize Go callgraphs in a clean way.

Start on a package-level and then "drill down" into each package to see what's really happening inside your code.

View package level calls (via RTA callgraph generation)

Single package/library view is still heavily WIP (via CHA callgraph generation)

• Overlay execution-trace/cpu-profile data on the graph.
• Find a new text-editor that doesn't wipe hours of work from disk.
• Avoid dying because of ice.

My code is WTFPL/Unlicense dual licensed. A Bunch of code is copied out of golang.org/x/tools, which is Apache Licensed.