5 ms·
This isn't about quality products, it's about being able to say you have a CLI tool because the other ai companies have one
by i_love_retros 1y ago
This isn't about quality products, it's about being able to say you have a CLI tool because the other ai companies have one
- clbrmbr 1y agoFast following is a reasonable strategy. Anthropic provided the existence proof. It’s an immensely useful form factor for AI.
- closewith 1y agoYeah, it would be absurd to avoid a course of action proven productive by a competitor.
- mike_hearn 1y agoThe question is whether what makes it useful is actually being in the terminal (limited, glitchy, awkward interaction) or whether it's being able to run next to files on a remote system. I suspect the latter.
- behnamoh 1y ago> This isn't about quality products, it's about being able to say you have a CLI tool because the other ai companies have one Anthropic's Claude Code is also installed using npm/npx.
- rs186 1y agoEh, I can't see how your comment is relevant ti the parent thread. Creating a CLI in Go is barely more complicated than JS. Rust, probably, but people aren't asking for that.
- frollogaston 1y agoThey wrote the CLI "GUI" in React using ink, which is all JS-only. I don't know what the Golang way of doing this would be, but maybe it's harder if you want the same result.
- rs186 1y agoThere are many GUI building libraries in Go. Sure, you wouldn't be writing JSX (and I agree it's an interesting idea), but it doesn't mean it's more any work to get things rendered in a terminal with other approaches, especially with these AI assistants to help you finish the boring parts.
- frollogaston 1y agoIf the UI is complicated at all, React is a well-established way to do that easily. The one-off tools will be harder, and even the AI won't know them as well as it knows React.
- frollogaston 1y agoWriting it in Golang or Rust doesn't really make it better