Looks very interesting, but seems to be excruciatingly slow at indexing Python projects. Ran it on https://github.com/fonttools/fonttools/tree/master/Lib/fontT... (~230 files) and it took 45 minutes while keeping all 16 cores of my Ryzen 1700 at full load, sometimes using ~16 GB of RAM. Exiting the application ends in a SEGV, but seemingly without consequences? Also, after moving the database files to a different folder and renaming the "source group", it now asks me run re-index everything. AAAARRRGHHH.

Absolutely amazing product! wish it supported more languages though.

Other than being a great and useful product, their Global Pricing is based on big-mac index is fantastic. To put this in perspective, the "standard" price of 744.47$ is twice the median wage in Afghanistan.

Never knew a product like this existed. This is a godsend for me as I navigate lot of old codebases.

I usually use PyCharm in a very similar manner, to browse others code locally. This is much more efficient compared to e.g. browsing/reading the code on GitHub. Whenever I spend more than a few minutes browsing some code on GitHub, I just clone the repo instead and open it in PyCharm. Finding some usages of some function, or simple searching for some string or so is much faster and more comfortable (also because the search on GitHub is so limited). I can only recommend this workflow to anyone who reads others source code. And reading others source code is anyway also something I would recommend everyone.

About Sourcetrail, I see from the homepage that it also has some additional graphical representation. Is this more helpful over what PyCharm already offers?

If so, maybe this also can be a feature request to PyCharm.

There exists one for Javascript as well:

https://github.com/Bogdan-Lyashenko/js-code-to-svg-flowchart

Including a VSCode extension (but it seems unmaintained):

https://marketplace.visualstudio.com/items?itemName=lucasbad...

Here is the release post that describes the Python integration a bit more detailed: https://www.sourcetrail.com/blog/sourcetrail_supports_python...

How does this compare to Code Maps in Visual Studio? Can anyone who has used both comment?

Oh my god, I've been looking for something like this for like a full year. This is awesome.

What frameworks did you use to create the UI?

Awesome! Will try without a doubt.

I tried the demo back when this was still called Coati. Very impressive, but not quite suitable for my current job. I didn't have time to fully evaluate it at the time, but these are my impressions from trying to use it on our codebase (I can't say exactly who we are due to NDAs).

My first criticism would be that the UI wastes a lot of space with all the curves and thick borders. Might be due to me using Vim most of the time, but I'm used to a higher text density. It also felt sluggish, but this might have been improved in the meantime, and also I used it on Linux which is notoriously bad for graphical responsiveness.

Second, the indexing was kind of slow. Our codebase is very far from the size of Chrome's, but it is a big commercial C++ project - something like 2M sloc (with comments). This was compounded by the fact that switching branches often led to nearly rebuilding a lot of files due to changes in often-used headers.

Third, it can only index one build configuration. Our single source tree is used to build several products and indexing only one build configuration is helpful, but often I need to know if changes necessary for product A will impact product B. It would be really nice if the indexing was split off into its own daemon and I could e.g. have three daemons looking over three build configurations on Linux, an additional remote daemon indexing the MacOS source, and further two running on a Windows host (possibly a VM). This might sound extreme and convoluted, but the kind of large C++ project where Sourcetrail would shine is the kind that has its own very opinionated idiosyncrasies.

Finally, it doesn't actually solve my most frequent use-case. Sourcetrail is great for browsing and understanding OOP structure of code. However, I am most often interested in exploring dataflow. I really want to know where a particular member of a struct is set, where the values in the expression come from, where those values are set, where the values in those expressions are from, etc. This can be accomplished with pretty much the same hierarchical interface that Sourcetrail currently has, but instead of classes and methods, the basic units should be expressions and values. Another useful feature would be "where is this value used" - say you have a member of a struct, or a method returning a constant value, and you want to know where the value of the member is used. Not where the member is used, because the value of the member is often copied around, but without being modified. I would really like something that can track through assignments to tell me where this value ends up. Right now Sourcetrail doesn't really cover this usecase better than Vim+ctags+rtags+ripgrep. Yes, this sounds a bit like "Dropbox is just sftp+rsync", but I couldn't make Coati work better for my usecase than my current setup.

I can't demand that dataflow analysis be implemented, because I can't promise that I'll use Sourcetrail even if it is, but a data-oriented view of code might be a worthwhile development to consider.

Sourcetrail dev here. Thanks for your extensive feedback!

A lot of things have changed since Sourcetrail was called Coati (about 2 years ago). We put a lot of work into improving indexing speed, handling multiple configurations/different languages within one project and reducing "sluggishness" in the UI. Sourcetrail runs now smoothly on code bases with multiple MLoC.

But I agree with your suggestion regarding data-flow analysis. That is what understanding unfamiliar source code often really comes down to. We also had some user requests to go that direction. We never really looked into this area so far, because it is a lot harder to collect the data (dynamic analysis) and it needs a whole new user interface.

While the data collection is solvable (Visual Studio debugger can do it, I think), I'm not sure whether it is really possible to come up with an effective user interface that shows which paths the different values take.

To explain why this is hard, let me use a metaphor: With data-flow you need to deal with a new dimension: time. Sourcetrail can handle dependencies between definitions really well, before the code is executed: space. What you want is a tool that combines the two into a space-time exploration tool of source code. Not sure if possible at all, but very interesting to think about. :)

+1 for dataflow analysis, though I'm thinking about dynamic languages and realising how tricky it would be to implement..