Hacker News Reader

Comment by metaltyphoon | Hacker News Reader

Do you really think that having this many issues is justifiable/ok?

https://github.com/anthropics/claude-code/issues

Those numbers don't really mean anything. Claude Code has millions of users, and that issue forum is the most obvious place for them to ask questions or request features.

If there were 11,000 open and confirmed bugs then yeah, that would mean the software is bad.

No one knows how many bugs claude has because Anthropic auto-closes Issues (or at least used to) if there isn't someone constantly pinging the issue every two weeks. I've contributed to several issues that were confirmed by several other people, which were they were auto-closed after people gave up confirming the problem without any response from Anthropic. They seemingly don't care if it isn't on fire or at least smoldering heavily, which seems really bad in my book if you're trying to make even reasonably good software.

> Those numbers don't really mean anything

IMO this is very dismissive. One example of probably many more, where software is used by millions and yet doesn't have this much being reported.

https://github.com/curl/curl/issues

curl isn't end-user software, and has a very small, well defined surface area.

curl is certainly a much more difficult problem to solve well, and does so without 30 million issues or whatever the CC codebase has

Curl is great, but I think you're vastly underestimating the surface area of CC.

It looks like it has more in: editor integrations, multiple guis and tuis, config variations, external systems (eg, git, mcps, curl-like requests?), statefulness (curl is "only" request response), inner runtimes (eg, sandbox per OS), sensitivity to its environment, possible side effects of its own execution, potential interaction combinations, etc.

Curl has hard system-level code requirements but it's design space feels more bounded and predictable to me.

This of course isn't an excuse for all bugs.

yes but there is a big difference between 100 sloppy features vs a handful of strongly and safely executed ones. it's not linear in effort.

> I think you're vastly underestimating the surface area of CC.

That is one of the reasons CC code is so low quality. The amount of extra unnecessary code just to implement it using React is by far the worst technical slop decision I've seen made by so called "software engineers" in a long time.

I dont't really know stats about such things, but I assume the adoption of CC has been insane compared to almost anything, and is also like two years old? Yeah, not surprised.

But also, if they all use 500 agents daily and latest models can "one shot" everything, one would think 5k issues are fixed in no time...

Havent used CC in some time, worked fine last time I tried.

> But also, if they all use 500 agents daily and latest models can "one shot" everything, one would think 5k issues are fixed in no time...

IMO, CC should be the poster child of what LLM coding should "feel" like. If things are so good why are there so many issues? Why can't they get a handle like other well-run projects? As you said, they have unlimited tokens so this project should be close to pristine as much as possible.

Reply on news.ycombinator.com