Live data from Hacker News

Asqi: A codebase explorer designed to help navigate and understand Git projects

dev.asqi.io

11–20 of 40 posts

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#11
post #6
post #3

The demo is not working for me: https://demo.dev.asqi.io/

Same demo not working for me, asks me to install a React App on the address bar in Chrome. No chance I'm installing something random.

Yeah you definitely don't need to install anything. I don't know how to deploy React apps apparently (will try to fix), but it's just a regular website and I would never ask users to expect anything else.

Update: it's because create-react-app creates manifest.json in public/, which causes Chrome to prompt you for this. I've deleted it in the latest container image and I'll redeploy once traffic dies down a bit.

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#12

tools like Greptile (which this seems close to) to understand Git projects were one time use for me (rendering monthly subscription pointless) once how to properly use github search especially also not sure about the web design i guess there are some tools where this works

I wanted to say, this is really thoughtful comment and thank you. I love getting ideas like this about the business model and product/market fit.

The second half of the product is a lot more about everyday features e.g. "whose branches collide with mine" or "what are all the upcoming changes in this module", that type of thing. I'm hoping that shores up the long-termism a bit. We'll have to see, though; this whole thing is kind of an experiment and it may just be a miss, or serve a very specialized use case. If you have more thoughts, I'd welcome them.

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#13
post #9
post #5

I’m wondering what computer language analysis tools are necessary to make this work for another language. The OG page supplies this info Supported languages ------------------- Asqi can provide file-level indexing for everything, and it provides semantic indexing for: + C/C++ + Java + Go + Rust + JavaScript/TypeScript + Python

It's actually pretty straightforward; we use tree-sitter for parsing and it takes me about 2-3 hours for each language. So I'm planning to add a lot more in the near future. If you have any that you find especially valuable, let me know and I'll see if I can prioritize them.

Kotlin would be awesome!

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#14
post #9
post #5

I’m wondering what computer language analysis tools are necessary to make this work for another language. The OG page supplies this info Supported languages ------------------- Asqi can provide file-level indexing for everything, and it provides semantic indexing for: + C/C++ + Java + Go + Rust + JavaScript/TypeScript + Python

It's actually pretty straightforward; we use tree-sitter for parsing and it takes me about 2-3 hours for each language. So I'm planning to add a lot more in the near future. If you have any that you find especially valuable, let me know and I'll see if I can prioritize them.

With regards to your call for interesting language support, I'd add a very low-priority suggestion for documentation and specification formats. Plain text, Markdown, simple HTML paragraphs and sections. If a new paragraph or sentence is added to a spec, or a MUST becomes a MAY, it'd be neat to surface the context of the change instead of a word/line diff.

As the Semantic History is not yet available, how do you envision it being displayed at the moment? What sort of information are you currently collecting? Is this tracked across the project history? To that end, are you building Tree-Sitter grammars and queries yourself, or are you using the pre-existing grammars and building the language support into Asqi?

For context, I've got a back-burner project that maps reimplemented code (manually mapped, with annotations or structured comments) to identifiable items in an upstream codebase and git repository. When the content of an item is changed upstream, affected downstream code could be flagged for review. It's still early in the design/prototyping phase, but it feels like there's some interesting overlap with Asqi.

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#15
post #9
post #5

I’m wondering what computer language analysis tools are necessary to make this work for another language. The OG page supplies this info Supported languages ------------------- Asqi can provide file-level indexing for everything, and it provides semantic indexing for: + C/C++ + Java + Go + Rust + JavaScript/TypeScript + Python

It's actually pretty straightforward; we use tree-sitter for parsing and it takes me about 2-3 hours for each language. So I'm planning to add a lot more in the near future. If you have any that you find especially valuable, let me know and I'll see if I can prioritize them.

Ruby with sorbet would be cool, and C#

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#16
I want to like this but I found the UI too confusing and didn't get anything out of the current experience.

I liked the BBS/ssh server intro and styling but you lost me at the jumpy, nested circular tree chart thingy. Maybe a boring rectangular treemap would work better? Even better if it was rendered in the terminal over ssh...

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#17
I like the speed and compactness of the UI.

Hopefully constructive feedback.

1. That message about upcoming feature obscures the code and is actually a big div taking the whole right side, from top to bottom, which blocks events like scrolling with mouse wheel. It's white so it looks like part of code but blocks scrolling of code.

2. those circular things are a gimmick in my mind. And acting on hover is confusing: I move the mouse and things flash wildly.

Give me a clear option to permanently hide the circular thingy.

Only act on click, not mouse over.

3. When I clicked on an enum definition (e.g. in postgres parser) I expected a way to see all places that use that enum. It's not possible or I'm missing something.

4. The "search everywhere" dialog is confusing. Again, a big circular thingy, invisible cursor so I don't even know I can type something and I don't know what I'm searching there. File names? I expect search to be full text search of all files.

5. I was confused by `C-u`. Now I get that it's `Ctrl-u` but make it more obvious . At least in help use the full `Ctrl-u` and add tooltips with full version.

6. The color of tabs is the inverse of what I expect based on pretty much all other software I use. A current tab should have the same color as the panel, so that it looks like it's part of it. Since panel is white, selected tab (e.g. History vs. Tree) should also be white. It's black. Or find some other way to make it clear which tab is selected.

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#18
post #17

I like the speed and compactness of the UI. Hopefully constructive feedback. 1. That message about upcoming feature obscures the code and is actually a big div taking the whole right side, from top to bottom, which blocks events like scrolling with mouse wheel. It's white so it looks like part of code but blocks scrolling of code. 2. those circular things are a gimmick in my mind. And acting on hover is confusing: I…

Thanks so much for writing this up, it's great! Let me get some coffee and I'll share some thoughts about where we are and where it's going.

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#19
post #12

tools like Greptile (which this seems close to) to understand Git projects were one time use for me (rendering monthly subscription pointless) once how to properly use github search especially also not sure about the web design i guess there are some tools where this works

I wanted to say, this is really thoughtful comment and thank you. I love getting ideas like this about the business model and product/market fit. The second half of the product is a lot more about everyday features e.g. "whose branches collide with mine" or "what are all the upcoming changes in this module", that type of thing. I'm hoping that shores up the long-termism a bit. We'll have to see, though; this whole th…

There's definitely room for a good product here. Idk about advanced use, but from a naive view, git UI and vscode blame plugins are awkward to use.

Re: Asqi: A codebase explorer designed to help navigate and understand Git projects

#20
post #17

I like the speed and compactness of the UI. Hopefully constructive feedback. 1. That message about upcoming feature obscures the code and is actually a big div taking the whole right side, from top to bottom, which blocks events like scrolling with mouse wheel. It's white so it looks like part of code but blocks scrolling of code. 2. those circular things are a gimmick in my mind. And acting on hover is confusing: I…

> I was confused by `C-u`.

That's the old fashioned, traditional way to represent shortcuts.

Example:

https://courses.cs.washington.edu/courses/cse351/16wi/sectio...

Post reply on HN