wasmtalk VS Sourcetrail

I've had very similar thoughts and have wrote about them here. I would be interested in discussing more.

https://github.com/brennancheung/wasmtalk

Some key takeaways from the above link:

- The programmer's tool should be a tool for manipulating an annotated AST (not text)

- There should be many different types of UX's for different scenarios, each maps to and from an AST in a UX that is optimal for the developer for that scenario

- We must be conscious of human brain limitations and cognitive psychology and work within those constraints

- "Reading" and "Writing" code should have different UX's because they are radically different use cases

- Use RPN. It models the real world. Humans are designed to manipulate their environment in an incremental manner seeing the result each step of the way. When we have to plan out and write code for an extended period of time, trying to play compiler in our head, we overload our brain unnecessarily and highly likely to make simple mistakes.

- Testing should be a first class citizen in the developer experience and indeed baked into how we develop at a fundamental level that it seems strange that they are even decoupled to begin with.

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.