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

61–70 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#61

Post by seviu »

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…

To be fair with Codex, you can use any harness you want with it. Access is not gatekeeper by a crappy full of slop electron app.

So just move to PI, or whatever.

Claude on the contrary, forces all plan users to use their horrible app, which, if you ever dared to use cowork, only once, will run a 2GB VM on app start, no f's given. at all.

Not justifying it. But if you use the official Codex app, thats on you. If you use the official Claude app, it's because you are forced to.

Sidenote unrelated to the post: since the Fable thing, and after serious thinking, I moved to open source models. I still have the basic OpenAI sub, but then easy lifting is now done elsewhere.

Re: Codex logging bug may write TBs to local SSDs

#62

Post by nicce »

hokkos wrote: post #58
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…

is it closed source ? i can see the rust code in repo contrary to the JS in claude code repo, are you mixing them up ?

Codex CLI is the main Rust code. There is Codex Desktop separately, using Electron and the same Codex CLI.

Re: Codex logging bug may write TBs to local SSDs

#63

Post by purpleidea »

I want to like codex, but the quality is just not very good, especially when compared to Claude.

It used to work okay, but a while back they landed a major regression for an entire team of folks I work with.

No response, no workaround.

https://github.com/openai/codex/issues/23762

Re: Codex logging bug may write TBs to local SSDs

#64

Post by r_lee »

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…

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage?

shouldn't this "agentic AI revolution" have long solved this already?

no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

Re: Codex logging bug may write TBs to local SSDs

#65

Post by kokada »

jofzar wrote: post #41
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…

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

Not that Claude Code is much better, I just hit this issue[1] because it seems setting DO_NOT_TRACK=1 seems enough to get a really strange behavior in the newest versions of CC.

[1]: https://github.com/anthropics/claude-code/issues/69238#issue...

Edit: I think I misunderstood OP, they're saying that CC is even worse and not better than Codex CLI.

Re: Codex logging bug may write TBs to local SSDs

#66

Post by cryo32 »

Imustaskforhelp wrote: post #45
cryo32 wrote: post #36

Earlier quoted context omitted.

Yeah. Here I am sitting on a major incident at our company because someone’s vibe coded shit went seriously wrong.

Can you talk more in detail if possible and are allowed to do so? I do know one instance of someone literally losing a job because they vibe-coded their way to prod. Their response/justification was: "The code wasn't written by me. It was written by Claude/Chatgpt" They hadn't done anything to the database itself but you betcha that there are some horror stories involving database, lack of proper backups and Vibe-cod…

I can say very little in detail but basically Claude doesn’t have any conceptual idea of order of operations and transactional guarantees which resulted in producing something that failed under normal load. There is an evidence chain to suggest it was asked to do this but did not and that wasn’t verified.

Our engineers are accountable for what they produce regardless of how so they are cleaning up the extensive mess this made. This will result in a very heated post-mortem meeting between the two factions in the company.

Re: Codex logging bug may write TBs to local SSDs

#67

Post by igleria »

r_lee wrote: post #64
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…

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

This is the biggest elephant in the room I have seen in my decade+ career. At the same time, look how bad Apple is in software compared to its hardware... It's not an AI only problem, it's almost like software in general gets a free pass on being very unsafe or low quality because no one wants to face the same "profit reducing red tape" that civil engineers or similar face.

Re: Codex logging bug may write TBs to local SSDs

#68

Post by fg137 »

r_lee wrote: post #64
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…

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

You are asking too many good questions.
Post reply on HN