Repository navigation
Replies: 3 comments
|
Thank you for asking. On CBM's side, the overlap is structural lookup: symbol search, call tracing, source snippets, and change-impact queries. That does not by itself establish that it replaces the particular navigation, diagnostics, editing, or search workflow you use elsewhere. I have not validated those tools head-to-head, so I would not recommend removing one on that basis. Which Java task are you trying to simplify? |
|
Thank you again for the comparison question. I have no new head-to-head validation to report. If you are still choosing a setup, one concrete Java task and what each tool currently contributes would let us discuss the overlap without assuming that structural lookup replaces diagnostics or editing. There is no recommendation here to remove a working tool. |
|
Thank you again for the discussion. If the overlap question remains, one concrete Java task and what each tool contributes would help avoid unsupported replacement claims. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Would this tool make the use of e.g. java LSP server / serena, or fff MCP redundant? Or would they all complement each other?
What about seemingly more similar graymatter? Edit: nope, graymatter is a different kind of product.
All reactions