12 points
3 hours ago
| 2 comments
| HN
dgellow
3 hours ago
[-]
A bit confused by the highlighted features. Is 6MB considered small? With that feature set that feels really large to me, even if we consider the go runtime is included. Why would I want a CLI tool like that to have MCP support? Why is there a sync feature, what is there to sync? Cannot I just copy my config file, similar to my other dot files? That feels pretty bloated to be honest

(The readme also read LLM generated, but I guess that just the new normal…)

reply
nvme0n1p1
3 hours ago
[-]
LLMs fall back on things like that when there's nothing good worth mentioning about a project. They simply emit tokens. If there are no good tokens they could emit, they emit bad tokens instead.

6.2MB - actually a bad thing

pure Go - irrelevant at best

no fzf - actually a bad thing

reply
AlecSchueler
3 hours ago
[-]
It's all over the README as well:

>Inline overlay — Opens below the cursor, not as a fullscreen app. Dismiss without trace. Pure ANSI escape codes, no libraries.

> Fuzzy search + typo tolerance — Damerau-Levenshtein distance catches typos.

Just that tone-deaf voice that can't tell what's useful information and what isn't but presents it all the same anyway.

Honestly what disappoints me about seeing this stuff come through unedited is that surely the human behind it had more time for checking over what was being communicated because they didn't spend the time writing the code etc? But they didn't, so what did they do? And now as a reader I'm expected to sift through and figure it all out?

I feel like this ship is sailing and I'm just turning into an old man shaking my fist at clouds but it's really sad to me that communication is become so fuzzy. Just throw whatever words up there and hope for the best.

reply
awoimbee
3 hours ago
[-]
I personally use fzf and I'm pretty happy with it, this seems to do a lot more but it's not clear what exactly ?
reply