Live data from Hacker News

GoCity – Code City metaphor for visualizing Go source code

go-city.github.io

11–20 of 37 posts

Re: GoCity – Code City metaphor for visualizing Go source code

#11

Very interesting! We built something very similar a few years ago for visualizing code complexity (or other metrics) over large code bases, it's also open-source: http://quantifiedcode.github.io/code-is-beautiful/ Here's e.g. the cityscape visualization of the Django codebase: http://quantifiedcode.github.io/code-is-beautiful/code-city/ We also did some 2D versions of the same graphs, which are often a bit easier to…

This is really neat, does your team/you actually use this in a meaningful way? Take a snapshot of a project occasionally to get an idea of whether it's getting unwieldy, etc.?

Re: GoCity – Code City metaphor for visualizing Go source code

#12
post #9
post #6

Earlier quoted context omitted.

similar load test is to hit github.com/golang/go

Yeah, that crashed mobile safari for me when I tried it earlier. I imagine kubernetes would be tough as well.

How does github.com/upspin/upspin compare?

Re: GoCity – Code City metaphor for visualizing Go source code

#13
post #11

Very interesting! We built something very similar a few years ago for visualizing code complexity (or other metrics) over large code bases, it's also open-source: http://quantifiedcode.github.io/code-is-beautiful/ Here's e.g. the cityscape visualization of the Django codebase: http://quantifiedcode.github.io/code-is-beautiful/code-city/ We also did some 2D versions of the same graphs, which are often a bit easier to…

This is really neat, does your team/you actually use this in a meaningful way? Take a snapshot of a project occasionally to get an idea of whether it's getting unwieldy, etc.?

We offered this as part of our SaaS product (now retired, https://github.com/quantifiedcode/quantifiedcode). The data was generated using a tool called "checkmate" (https://github.com/quantifiedcode/checkmate), which produced various metrics grouped by directory for each git commit of a project (in an efficient way). This data was then used to generate the visualizations.

An example for the data generated by checkmate can be found here:

http://quantifiedcode.github.io/code-is-beautiful/data/djang...

For a given git commit, checkmate only re-analyzed the files that changed and then recomputed all metrics on the fly using the new and existing file revisions, which would take only a few seconds to minutes even for very large projects.

Re: GoCity – Code City metaphor for visualizing Go source code

#14
Some kind of treemap [1] might be a better visualization option, 3D visualizations are notoriously hard to navigate. NDepend [2] is a code analysis tool for .NET which, among other things, uses treemaps to visualize code bases. There are also a versions for Java [3] and C++ [4].

[1] https://en.wikipedia.org/wiki/Treemapping

[2] https://www.ndepend.com/screenshots

[3] https://www.jarchitect.com

[4] https://www.cppdepend.com

Re: GoCity – Code City metaphor for visualizing Go source code

#15
post #6
post #5

If you want a test case for improving the rendering performance, try "github.com/juju/juju". It manages about 1 FPS on an iMac.

similar load test is to hit github.com/golang/go

Similar result to what is being described on Safari with this on Chrome - slows down to 1 fps, and some of the gray boxes to seem to be rendering with a red one.
Post reply on HN