Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

Post reply on HN
Print view View original

151–160 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#151

Post by chorkpop »

me551ah wrote: post #122
jofzar wrote: post #41

Earlier quoted context omitted.

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235

CLAUDE.md has been incredibly successful for them advertising wise. I wouldn’t expect them to admit AGENTS.md exists anytime soon.

Re: Codex logging bug may write TBs to local SSDs

#152

Post by iknowstuff »

jorl17 wrote: post #110
b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

Claude code (desktop) and Codex (desktop) are both absolutely dogshit pieces of software. I can't pick which one is worse. I'd be sort of ashamed to say I actively worked on them, regardless of how they can empower people. Cursor's new UI is similarly terrible. They're all slowly getting better, but too slow for my taste. They are incredibly slow in unpredictable ways, eat up memory at an insane rate, and just feel l…

I’ve been using Codex and Claude in Zed via ACP. Some bugs but overall very pleasant experience vs anything Cursor.

Re: Codex logging bug may write TBs to local SSDs

#153

Post by ljlolel »

jorl17 wrote: post #110
b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

Claude code (desktop) and Codex (desktop) are both absolutely dogshit pieces of software. I can't pick which one is worse. I'd be sort of ashamed to say I actively worked on them, regardless of how they can empower people. Cursor's new UI is similarly terrible. They're all slowly getting better, but too slow for my taste. They are incredibly slow in unpredictable ways, eat up memory at an insane rate, and just feel l…

That’s why I’m building an open source native Swift version: https://github.com/Lore-Hex/Quillcode

Re: Codex logging bug may write TBs to local SSDs

#154

Post by stellamariesays »

b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

[flagged]

Re: Codex logging bug may write TBs to local SSDs

#155

Post by ljlolel »

b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

Building an open source native swift version that doesn’t have that bug: https://github.com/Lore-Hex/Quillcode

Re: Codex logging bug may write TBs to local SSDs

#156

Post by oblio »

deathbob wrote: post #143
CharlieDigital wrote: post #74

Earlier quoted context omitted.

Anthropic were the progenitors of the Model Context Protocol. Claude Code does not fully implement the client end of the protocol. A protocol; a literal pre-defined spec that an agent should be able to one-shot. Neither does Codex. Codex does not implement MCP Prompts. (I want Codex to implement MCP Prompts because then we have one central way to ship skills from a server). The fact that neither platform can implemen…

It still boggles my mind that Anthropic would invent the MCP protocol but not fully implement it. Especially when fully implementing it (prompts, resources, tools) is easily done in harnesses that don’t ship with MCP but allow good extension / modification like Pi. Claude not being able to see its own usage or self invoke slash commands is also very frustrating.

> It still boggles my mind that Anthropic would invent the MCP protocol but not fully implement it.

https://www.joelonsoftware.com/2002/01/06/fire-and-motion/

> Do they just want to force you to keep busy reacting to their volleys, so you can’t move forward?

Re: Codex logging bug may write TBs to local SSDs

#157

Post by wafflemaker »

inigyou wrote: post #78
Otek wrote: post #76

Earlier quoted context omitted.

Already got replaced at world top tier tech jobs. „True SWE” will be niche / luxury soon, just like real woodworking vs IKEA

Software is freely duplicable unlike wood. IKEA could be mass producing copies of the most beautiful chair in the world just as easily as it produces copies of something a 5-year-old drew in freecad.

>something a 5-year-old drew in freecad

Ikea series of plush toys based on children drawings were actually very cool. Not drawn in frecad though, just plain old crayons on paper.

https://digitalsynopsis.com/advertising/ikea-childrens-drawi...

Re: Codex logging bug may write TBs to local SSDs

#158

Post by cozzyd »

varjag wrote: post #82
jofzar wrote: post #41

Earlier quoted context omitted.

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Right, just yesterday I found my laptop kinda hot. And what do you think, it was good old Claude deciding to load a few cores with completely idling prompts.

Yeah, somehow claude-cli sitting in a tmux session doing nothing uses my laptops battery twice as fast. Powertop suggests a ton of wakeups, but why? Is it busy polling the input or something?

Re: Codex logging bug may write TBs to local SSDs

#160

Post by epistasis »

iLoveOncall wrote: post #102
jofzar wrote: post #41

Earlier quoted context omitted.

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Surprisingly Kiro is fine (I work at Amazon but not at all on the Kiro team). I prefer it to anything else I've tried (except Amazon Q Developer in IntelliJ, but it's now deprecated).

Kiro is surprisingly good, if the interface for saving and resuming was slightly more reliable, and there was the hope of remote sessions, I'd probably switch to it full time. I vastly prefer it to having to fight against buggy force-fed features like UltraPlan or whatever.
Post reply on HN