I really want something like this for heterogenous codebases. Maybe along the lines of ollydbg and ida but for "reverse" engineering Ruby, python, and go.
Show HN: Sourcetrail – Get productive on unfamiliar source code
21–30 of 119 posts
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#22Looks cool! This hits a pain point of mine working in a legacy Python and C/C++ codebase. Any plans for Python support?
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#23I doubt you could ever get something like this working for Ruby, which is where it is actually badly needed.
Yes, dynamically typed languages are much harder to tackle :/
You don't need it to be fully automated. For dynamic languages you would have people in the loop to annotate the parts the tool couldn't figure out.
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#24Can you please share the roadmap for adding new language support?
To be honest: We have not decided what language we will pick up next. Our first priority is to improve on our Java coverage. In a few months we should be ready to choose our next language. We are thinking about either tackling Python or implement support for a more recent language like Kotlin, Swift or Go.
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#25I used Sourcetrail a few months ago to figure out a ugly ball of embedded C code that I needed to reimpliment. Sourcetrail was super helpful for this. It paid for itself in an afternoon.
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#26Earlier quoted context omitted.
Yes, dynamically typed languages are much harder to tackle :/
You don't need it to be fully automated. For dynamic languages you would have people in the loop to annotate the parts the tool couldn't figure out.
This seems like no better off. Documentation is historically always out of date the second its written. The same would be true for annotation.
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#27Earlier quoted context omitted.
You don't need it to be fully automated. For dynamic languages you would have people in the loop to annotate the parts the tool couldn't figure out.
This seems like no better off. Documentation is historically always out of date the second its written. The same would be true for annotation.
Guess you could have some assertions together with the annotations to make sure things are up-to-date. Then integrate those tests with your CI of choice and it should be a bit easier to keep up-to-date.
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#28I used Sourcetrail a few months ago to figure out a ugly ball of embedded C code that I needed to reimpliment. Sourcetrail was super helpful for this. It paid for itself in an afternoon.
Thank you for the kind words! We are always happy to hear from a satisfied customer :)
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#29Looks cool! This hits a pain point of mine working in a legacy Python and C/C++ codebase. Any plans for Python support?
Happy to hear that you like it! Full support of Python won't be easy but maybe we could tackle this one in stages. Implement highly demanded features in a first Python release and improve on that later on.
Re: Show HN: Sourcetrail – Get productive on unfamiliar source code
#30Any plans to support Kotlin ?
Kotlin is definitely on the shortlist for the next language to be supported! Which language we'll pick up exactly depends on the landscape of available tools for that language. Kotlin is pretty new so I guess that there could be a need for Sourcetrail :)
If you ever go that route and you plan or using/creating some open-source components I would be very interested on hearing more (I am a JavaParser/JavaSymbolSolver contributor)