241–250 of 296 posts
Earlier quoted context omitted.
I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.
Symlinks are a pain if you're on Windows, I'd rather not bother with them.
How so?
Earlier quoted context omitted.
Not only Codex, but I can't leave ChatGPT app in macOS open for few hours, because it will consume 60 gigabytes of RAM over time and crashes all the apps. Mindboggling. Or can't use Google's AI Studio in browser because it takes 100% CPU. Need to write own app for everything???
the damn chat.openai.com webapp lags a lot as well on long chats, typing takes so long.
The entire conversation sits in the DOM.
Shocking. Been open a week and AFAICT just silence from OpenAI. I just find it baffling. You'd think that these vendors would be very sensitive to this sort of issue. I mean, surely they have multiple agents hooked up to github monitoring potential issues and proposing fixes, right? ...right? Surely it should be trivial for them to have their own tools spinning away trying to fix all the github issues in real time...
They're pretty bad about fixing issues it seems. My favorite is #2472 which they demonstrated "fixing" on stage on the release of GPT 5, but the ticket is still open and the "fix" hasn't been merged. The original blog that flagged this fact https://blog.tymscar.com/posts/openaiunmergeddemo/ and the issue: https://github.com/openai/openai-python/issues/2472
> Permission bypass when commands are chained with &&
At one point they fixed their auto stale bot closing bugs but, hey, guess that wasn’t long lived.
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…
That bug caused untold grief for multi-user session hosts / terminal servers / Citrix XenApp for a better part of a decade. Way before slopware!
People forget that software written by people is… even worse.
It’s like the self driving car debate: sure, the robot taxis will kill people on occasion, but people kill people regularly.
Earlier quoted context omitted.
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"?
Because vibe coding is a toy… thats the secret. You can use it to accelerate development certainly, but that requires careful change->review cycles. The developer still needs to be in heavy control, versus vibe coding having an agent own the code base.
Slightly better than the claude code "feature" that deletes all your session context and transcripts older than 30 days old.
At least that's a decision vs a bug.
Earlier quoted context omitted.
Every time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy that would have caught this
I'll acknowledge that this is probably not likely to get caught. Integration testing could/should catch this, especially for a client side app. A simple constraints is a good thing. "Our app shouldn't use more than 50mb of ram, or use 3gb of disk space."