Viewing profile — zxt_tzx

My previous HN post ( https://news.ycombinator.com/item?id=43299659 ) got some traction, and several folks reached out asking for the source code, so here it is! Rumor has it a cer…

Thank you for the comment, compared to you I have only touched the bare surface of this quite complex domain, would love to get more of your input! > building HNSW indices in Postg…

I'm glad you found it helpful :)

> And overall, the fewer people use CF (or another provider of their size) the better. I understand your sentiment, but I vehemently disagree. The cloud provider space has rapidly …

After this failed experience with SemHub, I am actually thinking of building something like this, for open source maintainers like you are definitely the ICP! (nuqs seems really co…

Thanks for sharing! Do you have more details to share, e.g. did you just have a vector db, or did you have a main db as well? In my research, Qdrant was also the top contender and …

Ah I was doing semantic search of GitHub _issues_, not the actual code on GitHub. For code search, I have used grep.app, which works reasonably well

> There’s so much complexity that comes with keeping your vector db in sync with you main db (especially once you start filtering with metadata) Ohh do you speak from experience? I…

oh wow that's super cool, I tried it and it's very fast indeed. thanks for sharing! will spend more time to understand how it's implemented

Thanks for the feedback, to be honest, my own experience is actually very similar to yours. The original pain point probably only exists for small minority of open source maintaine…

> Have you looked into chunking (breaking input into smaller chunks and doing vector search on the chunks)? Ohh I had not seriously considered this until reading this. I could have…

> it's weird you consider this a failure. you spent a few months and learned how to work with embedding models to build an efficient search. the fact that your search works well is…

Ohh apologies, I think there was a bug that led to the Internal Server Error, please try again, I _think_ it should be working now! > I think a project like yours is going to be he…

Totally fair point. Thanks for taking the time to read through it! I guess I didn't want to use a VPS and then have to switch to something else if the product really worked, but I …

Author here. Over the last few months, I have built and launched a free semantic search tool for GitHub called SemHub ( https://semhub.dev/ ). In this blog post, I share what I’ve …

I built SemHub because issues search on GitHub sucks. We probably use it so frequently each day that we've developed schlep blindness to how much it sucks. For example: - No way to…

I built SemHub because I was not satisfied with the default search experience on GitHub. For example: - No way to easily search across multiple repos - No way to easily see open an…

It's always a little dubious when modern people pretend to have high confidence about the behaviors of long-dead people to serve their modern purposes. (Another example: oh you're …

I met one of the founders of Coder.com, he's a really cool dude. It's a pity that it is a product aimed more at enterprises than individual developers, else it would have far more …

Mildly interesting that the author runs a media relations company in SF. On the one hand, I am sympathetic to the general perspective of the original article. On the other hand, th…

Interesting stuff. We use MemoryDB as the underlying service for BullMQ, a NodeJS queue that’s built on top of Redis. We trade off a bit of speed and cost (MemoryDB costs more than…