Live data from Hacker News

JSCity – JavaScript code visualizations using Three.js

github.com

11–18 of 18 posts

Re: JSCity – JavaScript code visualizations using Three.js

#11
post #4

It's unfortunate that the author has chosen to wait with giving access to the source code, insisting that it still needs to be "cleaned up". I can understand the reasons (in most cases it seems to be vanity), but it would often be best to just give access and clearly mark it 'work in progress'. Open source miracles may happen.

What are "open source miracles" for early-developed project?

Re: JSCity – JavaScript code visualizations using Three.js

#12
post #4

It's unfortunate that the author has chosen to wait with giving access to the source code, insisting that it still needs to be "cleaned up". I can understand the reasons (in most cases it seems to be vanity), but it would often be best to just give access and clearly mark it 'work in progress'. Open source miracles may happen.

The problem is most people just criticise/tear-down instead of actually improving open-source projects (just read the Show HN section here...). Building open source projects requires a positive attitude and early stage comments can be discouraging.

Re: JSCity – JavaScript code visualizations using Three.js

#16
Before I read the details I figured it was a picture of number lines committed per contributor. With tall monoliths being single contributor projects, and urban sprawls being multi committer projects. Now, I wonder what that visualization would look like for all these different projects.

Re: JSCity – JavaScript code visualizations using Three.js

#17
post #5

aside from looking great - what does this tool give us?

A quick visual overview of how complex a codebase is

I cannot imagine someone on a dev meetup saying "we ended up choosing knockoutjs and backbone over angular because their models were more visually appealing than angular's city model" .. this is what I mean when I ask "what do I get out of this?"
Post reply on HN