HN user

kernelsanderz

226 karma
Posts3
Comments75
View on HN

I’ve been excited about lancedb and its ability to support vector indexes and efficient row level lookups. I wonder if this approach would work for their design goals and still allow broader backwards compatibility with the parquet ecosystem. Have been intrigued by Ducklake, and they’ve leaned into parquet. Perhaps this approach will allow more flexible indexing approaches with support for the broader parquet ecosystem which is significant.

No, there's a configurable system prompt which is:

Return commands suitable for copy/pasting into \(shell) on \(uname). Do NOT include commentary NOR Markdown triple-backtick code blocks as your whole response will be copied into my terminal automatically.

The script should do this: \(ai.prompt)

And then you type your prompt in, and it returns the answer. And then you can choose to edit the command that gets returned or execute it directly.

So essentially what you'd do if you were using the API directly, just more convenient.

I'd be fascinated if you could share your insights from using this. Where does the pricing fall down? And is the latency/throughput a big improvement for this use case? (ie. externalizing a search index).

Very excited about being able to build scalable vector databases on DiskANN like turbopuffer or lancedb. These changes in latency are game changing. The best server is no server. The capability a low latency vector database application that runs in lambda and S3 and is dirt cheap is pretty amazing.

It's not really. It was unfortunate timing. This used to be called GPT-Index, and then they changed names before Meta released their LLM. So their use predated it.

I feel sorry for the amazing team behind this great library. Changing names is hard.