I admire and respect these types of decisions so much.
> In late 2015 we founded the start-up “Coati Software” and started building “Sourcetrail” as a commercial developer tool. We had the vision for Sourcetrail to become the go-to developer tool for reading and understanding all sorts of unfamiliar source code. And of course to become rich and famous on the way.
> Four years passed, and even though Sourcetrail slowly became known and regarded for its advantages in software exploration, it was still only used by a minority of software developers around the world. And we didn't get rich. Not even close. Instead we started losing money on the project by that time. Despite that, we didn't want to follow other companies in the field and go for higher and higher prices, because, as you remember, our goal was to bring the benefits of Sourcetrail to every developer, and not just benefit a few people in a handful of companies.
> But we didn't want to shut down everything and forget about Sourcetrail either. So we decided to steer away from our commercial license model and all the company internal secrecies and bring Sourectrail out in the open.
...
> Of course we have acquired a lot of knowledge while making Sourcetrail and it would be a waste to just open-source the codebase and walk away. We really want to continue working on Sourcetrail. That's why we set up this Patreon page. Here you can help us fund the time we put into further development of Sourcetrail.
The Smalltalk world also provides such tooling. Which offers a lot more flexibility on how to visualize source code. Unfortunately though it requires quite some effort to learn and use. But once you got the hang of it it's pretty awesome to browse source code and discover it's overall structure. And it allows you to ask more specific questions about the code and visualize the results as you see fit. Which can help a lot in actually finding not so good abstractions and architectural decisions.
sourcetrail is the only tool that would enable me to master the entire Firefox 52 and Chromium source code such that I can correctly insert instrumentation hooks in various part of the code, notable JavaScript.
While I paid for the commercial license, I am not disappointed in the slightest.
A must have for deep diving into a project with little or no design document.
Tangent question, How does small open source tools get sponsorship from the likes of Google and DigitalOcean? Who approaches who? is there some type of formal process?
Traversing and displaying code as a graph is indeed the primary use case for Sourcetrail. It's documented at https://www.sourcetrail.com/documentation/ You can also click any part of the code to navigate the graph and vice versa. If you have enough code that this sounds useful, and run a supported language, you'll love it for what it does. And yes, I'm aware that, for Java especially, IDEA has a number of similar code navigation and code graph features. Try both and see which you prefer. :)
The ability to use it when you don't want to run IDEA?
Sourcetrail can run on a server, and you can navigate a large codebase from a 10-year old laptop with little RAM. Or you might be using a different IDE for your embedded C codebase. Etc.
Edit: I've been wanting something like this for ages. Sometimes, I'd draw graphs on paper (similar to what Sourcetrail is doing) to make sense of code. Even my code :).
Ruby is so dynamic that code navigation is not easy. To resolve a method which is implemented via method_missing() in one of base classes, with respond_to?( ) in another base class, you need to instantiate the class hierarchy first and pretend-run some class methods.
Navigation in a statically-typed codebase is much much easier to implement.
Python's been implemented and works well enough with sane codebases. I imagine given Ruby's strong use of conventions, common usages could be covered easily given time.
