361–370 of 464 posts
Earlier quoted context omitted.
At least Gemini and Claude constantly break down with scrolling in various Linux terminals, something which was solved by countless TUIs decades ago. I think a lot of the people prasing Claude & co are on Macs.
I haven't seen the scrolling glitch in months, where previously it was happening multiple times a day. Also haven't seen anyone complain about it in quite some time. Pretty sure they have resolved that.
Earlier quoted context omitted.
Check out `print.ts` to see how "more LOC" doesn't mean "more polished"
Okay, I'm looking at it. Now what? This file is exactly what I'm talking about. Take the loadInitialMessage function: It's encumbered with real world incremental requirements. You can see exactly the bolted-on conditionals where they added features like --teleport, --fork-session, etc. The runHeadlessStreaming function is a more extreme version of that where a bunch of incremental, lateral subsystems are wired togeth…
Author here. I built this in a few hours after the Claude Code leak. I've been working on my own coding agent setup for a while. I mostly use pi [0] because it's minimal and easy to extend. When the leak happened, I wanted to study how Anthropic structured things: the tool system, how the agent loop flows, A 500K line codebase is a lot to navigate, so I mapped it visually to give myself a quick reference I could come…
Earlier quoted context omitted.
> Claude Code is an interface to using AI to do any computer task Claude Code is quite literally a wrapper around a few APIs. At one point it needed 68GB of RAM to run and requires 11ms to "lay a scene graph" to display a few hundred characters on screen. All links here: https://news.ycombinator.com/item?id=47598488 > while a 3D game just lets you shoot some bad guys, so surely the 3D game must be done in fewer loc.…
Your claim was that they could implement the same app in 50k lines of code. A cursory glance at the codebase shows that it's not just a wrapper around a few APIs.
Earlier quoted context omitted.
Okay, I'm looking at it. Now what? This file is exactly what I'm talking about. Take the loadInitialMessage function: It's encumbered with real world incremental requirements. You can see exactly the bolted-on conditionals where they added features like --teleport, --fork-session, etc. The runHeadlessStreaming function is a more extreme version of that where a bunch of incremental, lateral subsystems are wired togeth…
The file is more than 5000 lines of code. The main function is 3000. Code comments make reference to (and depend on guarantees in connection with) the specific behavior of code in other files . Do I need to explain why that's bad?
You don't have to explain why there might be better ways to write some code because the claim is about lines of code. It could be the case that perfectly organizing and abstracting the code would result in even more loc.
Earlier quoted context omitted.
> they break at large enterprise repos. I don't know where you get this. you should ask folks at Meta. They are probably the biggest and happiest users of CC
You mean the company where engineers ask chat bots to write chess games in their spare time in order to hit their AI usage requirements? That Meta?