Fair point — I removed that line just now. I'm a solo dev and I use AI for the docs; sometimes it sounds like an ad and I don't catch it. The benchmarks are real though, I ran them all myself. Try the software and tell me if something is wrong.

Yes, I use AI to help me build and write docs — solo dev, I'd be stupid not to. The benchmarks are real though: free Oracle ARM box, my laptop, a cheap VPS. I ran them all myself, including the ones that went badly (they're in the README too).

But if you didn't care enough to write the docs yourself, why are you submitting it for discussion?

Are you seriously expecting humans to spend their time and effort and discuss your AI written docs that you literally admit you'd be "stupid" to have spent effort on yourself?

That's really condescending of you.

It seems pointless to me to stir up conflict or engage in unnecessary arguments; I have simply expressed my personal view—namely, that I value the utility of artificial intelligence, which I sometimes use to kickstart new projects (projects that can certainly be supplemented with different types of input in the future). I believe this is an innovative, open-minded, and forward-looking approach. If you disagree, you are free to hold your opinion, but I do not share it.

For what it's worth: the feedback in this thread found three real bugs that were fixed, tested and shipped within 24 hours — that's the part of the discussion I care about.

"For what it's worth" ? Yeah for what it's worth to you, you mean.

You submitted and expected people to read an article that you say you would have been stupid to write yourself, that's quite condescending, and just because you got something worth your while out of that doesn't really make it okay.

That is genuinely a good callout — it is worth stopping here.

As a web developer, the local web server UI idea sounds like the natural next step. Since you're already using Ink/React for the TUI, the component model should map well to a browser-based UI. The git-as-database approach is elegant — curious to see how it evolves.

Thank you! I too am excited about next steps. There are a lot of interesting paths to explore still, and I do agree that the web interface would be a natural evolvement.

I know of a few projects that have used Git as a database to parse ETF flow data after extracting it and saving it in JSON or CSV format.