Sourcetrail VS Stateless

I wish something existed in this space. I used Coati Software's Sourcetrail for a couple of years. Unfortunately it was discontinued. It was a wonderful piece of software that indexed a code repository, and exposed an interface to explore it interactively. At least for me, it significantly improved the understanding and legibility of code.

The code is in an archived state (https://github.com/CoatiSoftware/Sourcetrail). Searching for the software on Google shows some screenshots.

I think it might make large scale code visualization in a similar way to how SourceTrail does it more feasible: https://github.com/CoatiSoftware/Sourcetrail

Sourcetrail: Free and open-source cross-platform source explorer https://github.com/CoatiSoftware/Sourcetrail

Yep souecetrail https://github.com/CoatiSoftware/Sourcetrail

I've used https://github.com/CoatiSoftware/Sourcetrail in the past for some bits of the legacy code project I'm on. I also use vim and cscope for day to day navigation but it's harder to get a big picture with those alone.

Sourcetrail?

Does it strive to do what Sourcetrail used to ?

You could always try using Sourcetrail. Unfortunately the open source project is now archived but it should still help you get insights into your code.

I like this method and state machines in general. Makes it more easier to reason about complex software. Also, ithe f the state machine gets bigger (more states) in the past I have used the Stateless library which is very good. But what you described above is perfect for managing the state of a menu system.

After using stateless for three years, my conclusion is that I cannot imagine a scenario, where it makes sense to use it.

This is a great article. Here is the Stateless library he is writing about. The link to the library is kind of buried in the middle of a sentence.

Yes! And we're using one. https://github.com/dotnet-state-machine/stateless We're creating the configuration dynamically based on how the user wants his workflow to work.

Stateless is my go-to state machine library for .NET. It's reasonably advanced but can also be very simple if you don't need the more advanced features.

I'm playing around with this library for a medium sized state machine I'm setting up, and it has this functionality. I think explicit state machines are a good use-case for having an actual diagram, since they can take up enough space that it becomes hard to build a mental map from reading the code due to locality issues.