Live data from Hacker News

Codex is wearing out our devices

old.reddit.com

21–30 of 39 posts

Re: Codex is wearing out our devices

#21

Earlier quoted context omitted.

Yes, they have a finite number of writes. The controller keeps track of this so you can even see what % of your SSD life is remaining in that sense.

Interesting, thanks, had no idea

There are also some cases where this can be magnified by certain write patterns or system behaviours.

I think there was a case of Teslas having these sorts of failures at one point due to them writing logs quite aggressively.

Another example was MacOS causing rapid wear due to virtual memory swaps if I recall on devices with smaller amounts of RAM.

Re: Codex is wearing out our devices

#22

> Codex Desktop for macOS triggers a persistent macOS Gatekeeper/SystemPolicy loop after launch. As a Linux guy, I recently did some macOS development and was incredibly annoyed by the "security" features, which seem designed to shift blame for security issues from Apple to users. macOS is constantly throwing up security screens and warnings about completely normal programs the user knowingly installed and trusted. I…

Fully disagree. I actively want to know when a program tries to access my hard drive and stuff…

Re: Codex is wearing out our devices

#23

> Codex Desktop for macOS triggers a persistent macOS Gatekeeper/SystemPolicy loop after launch. As a Linux guy, I recently did some macOS development and was incredibly annoyed by the "security" features, which seem designed to shift blame for security issues from Apple to users. macOS is constantly throwing up security screens and warnings about completely normal programs the user knowingly installed and trusted. I…

I’ve been developing on MacOS for years and don’t think I’m familiar with what you’re talking about. I’m familiar with the warnings, but hardly ever see them.

Re: Codex is wearing out our devices

#24

Earlier quoted context omitted.

Interesting, thanks, had no idea

There are also some cases where this can be magnified by certain write patterns or system behaviours. I think there was a case of Teslas having these sorts of failures at one point due to them writing logs quite aggressively. Another example was MacOS causing rapid wear due to virtual memory swaps if I recall on devices with smaller amounts of RAM.

Those Teslas were controller-less SSDs IIRC, common in the cheap embedded world.

Modern proper SSDs for computers do their best to spread out the writes (TRIM, and other features). They still wear out of course, nothing can beat physics. But if you buy a 2TB drive, there's a lot of room to spread out the write cycles that a normal user probably never has to worry about (no normal user is going to hit 500TBs of writes that breaks a modern 2TB SSD write balancing algorithm)

But it probably should be noted that embedded controller-free SSDs have significant write amplification issues. Embedded systems assumed you were trying to save money and/or compute... and also assumed you didn't do too many writes. So they really weren't designed for the write cycles that Teslas logging system did.

Re: Codex is wearing out our devices

#26
post #22

> Codex Desktop for macOS triggers a persistent macOS Gatekeeper/SystemPolicy loop after launch. As a Linux guy, I recently did some macOS development and was incredibly annoyed by the "security" features, which seem designed to shift blame for security issues from Apple to users. macOS is constantly throwing up security screens and warnings about completely normal programs the user knowingly installed and trusted. I…

Fully disagree. I actively want to know when a program tries to access my hard drive and stuff…

I understand the motivation, but the implementation results in little more than security theater in practice.

If you say "yes", the program can do almost anything and you'll have no idea what it's actually doing. If you say "no", you often can't use it for its intended purpose.

They took the iOS model and applied it to their desktop OS and it's just lazy and broken.

Re: Codex is wearing out our devices

#27

> Codex Desktop for macOS triggers a persistent macOS Gatekeeper/SystemPolicy loop after launch. As a Linux guy, I recently did some macOS development and was incredibly annoyed by the "security" features, which seem designed to shift blame for security issues from Apple to users. macOS is constantly throwing up security screens and warnings about completely normal programs the user knowingly installed and trusted. I…

I’ve been developing on MacOS for years and don’t think I’m familiar with what you’re talking about. I’m familiar with the warnings, but hardly ever see them.

I meant distributing software for macOS.

Re: Codex is wearing out our devices

#28
post #6

This reddit thread is devoid of any useful information. Just fear and speculation.

A Github issue with actual data instead of just someone reposting info: https://github.com/openai/codex/issues/28224 Previously discussed: https://news.ycombinator.com/item?id=48626930

Looks like the issue was closed?

Re: Codex is wearing out our devices

#29

> Codex Desktop for macOS triggers a persistent macOS Gatekeeper/SystemPolicy loop after launch. As a Linux guy, I recently did some macOS development and was incredibly annoyed by the "security" features, which seem designed to shift blame for security issues from Apple to users. macOS is constantly throwing up security screens and warnings about completely normal programs the user knowingly installed and trusted. I…

It is super annoying when you first set up a Mac and is really over the top. Definitely geared more towards the average user rather than developers. But, once you get through the barrage of approvals during initial use you're basically good to go for the lifetime of that machine. That said, I really wish there was a "I know what I'm doing" checkbox to avoid a lot of that BS...

Re: Codex is wearing out our devices

#30

Earlier quoted context omitted.

I’ve been developing on MacOS for years and don’t think I’m familiar with what you’re talking about. I’m familiar with the warnings, but hardly ever see them.

I meant distributing software for macOS.

That’s fair. What’s the Apple-recommended way to avoid this? I interact with a lot of software and tend not to hit it but I also don’t really interact with downloaded executables
Post reply on HN