Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Sourcetrail – Get productive on unfamiliar source code

sourcetrail.com

Post reply on HN
Print view View original

71–80 of 119 posts

Re: Show HN: Sourcetrail – Get productive on unfamiliar source code

#72

Post by dbcurtis »

nebucnaut wrote: post #24
peternicky wrote: post #15

Can 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.

Seems to me there is probably a huge amount of legacy Python code around that people need to explore. In fact, I've spent the entire day so far creating some so that we have enough legacy Python code around in a couple more years. Wouldn't want to run short.

Re: Show HN: Sourcetrail – Get productive on unfamiliar source code

#75

Post by rasjani »

jschwartzi wrote: post #62
rasjani wrote: post #40

Earlier quoted context omitted.

Compile commands ? Please Yes?

There is also a tool called Bear which will generate compile commands from Make-based builds, in case you were wondering. I've used it with some success. https://github.com/rizsotto/Bear

Im well aware of bear. Works fine in some cases, not so well in others. Author is also doing scan-build replacement in python which imho is far superior to bear.

Re: Show HN: Sourcetrail – Get productive on unfamiliar source code

#76

Post by kuangye »

ensiferum wrote: post #67
kuangye wrote: post #64

Has anyone run a large codebase like chromium with this tool? Is the indexing looking at what's compiled like libclang or is it static like gtags?

I'd imagine it's going to violently shit itself. Chromium has pretty good online code search btw.

Yes, but not the kind of visualization and calling stack shown by SourceTrial. Some of the code is 10 layers deep where the stuff actually happens with many complicated usage of inheritance, which I figure is where this kind of tool can shine.

Re: Show HN: Sourcetrail – Get productive on unfamiliar source code

#78

Post by egraether »

agentgt wrote: post #54

Just a feature request if it isn't already in the works: Runtime analysis of code that actually matters ie live code . Often its hard to figure out what in the code base actually matters. Debugging is still sort of difficult and dead code is really hard to find and get rid of. Particularly if reflection is used heavily which it almost always is these days. Otherwise (IMO) as a Java developer IntelliJ and Eclipse are…

Thank you for your input! I wouldn't call it a feature request though, I'd say it's another tool. But, you are right, exploration of dynamicly analyzed code would also greatly benefit understanding.

Re: Show HN: Sourcetrail – Get productive on unfamiliar source code

#79

Post by alkonaut »

ska wrote: post #57
alkonaut wrote: post #52

Website feedback: Supported languages is the #1 most important piece of info about this software. It should be front and center and probably repeated a few times already on the landing page.

This may be a result of your feedback, but for me looking just now it it front and center: "Sourcetrail - A cross platform source explorer for C/C++ and Java"

Haha there it is. Who said whining on HN doesn't change the world.

Re: Show HN: Sourcetrail – Get productive on unfamiliar source code

#80

Post by Shank »

nebucnaut wrote: post #24
peternicky wrote: post #15

Can 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.

Seems to me like the obvious choices would be languages that have large, long standing legacy codebases. Swift code is going to be relatively tight just because it's so recent, whereas something like C# isn't.
Post reply on HN