Sourcetrail: Free and open-source interactive source explorer
github.com
github.com
> 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.
https://modularmoose.org/moose-wiki/ http://themoosebook.org/
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.
They don't seem to be making enough on Patreon even for part-time work yet.
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 :).
Navigation in a statically-typed codebase is much much easier to implement.