gpt5 has always been about making a "collection of models" work together and not about model++. This was announced what, a year ago? And they delivered. Capabilities ~90-110% of their top tier old models at 4-6x lower price. That's insane!
gpt5-mini is insane for its price, in agentic coding. I've had great sessions with it, at 0.x$ / session. It can do things that claude 3.5/3.7 couldn't do ~6 months ago, at 10-15x the price. Whatever RL they did is working wonders.
No, it wasn’t. Have you read and listened to Altman’s hype around GPT-5 from a year ago? They changed the narration after the 4.1 flop, which they thought would be GPT-5, and it seems some people fell for it.
> Capabilities ~90-110% of their top tier old models at 4-6x lower price
Maybe they finally implemented the DeepSeek paper.
For anyone familiar with Chinese culture, history, and mindset, and who views China through that lens rather than a Western one, the probability of this is lower than the probability of Intel’s collapsing entirely in the next two years.
“Supreme excellence is to subdue the enemy without fighting.”
“Victory without unsheathing the blade.”
“If swords are clashing, strategy has already failed.”
It’s reasonable that he might be a little hyped about things because of his feelings about them and the methodology he uses to evaluate models. I assume good faith, as the HN guidelines propose, and this is the strongest plausible interpretation of what I see in his blog.
Dead Comment
And yet Go violates the definition they give -- it doesn't prevent out-of-bounds accesses. (And just to be sure we're talking about the same thing, I'm specifically talking about Go here. All the other languages on their list are actually memory safe, as far as I know.)
> you have to demonstrate a plausible scenario in realistic code where an attacker controls both the value and the address it's written to.
So your definition of memory safety includes some notion of "plausible" and "realistic"? Neither https://www.memorysafety.org/docs/memory-safety/ nor Wikipedia have such a qualification in their definition. It would help if you could just spell out your definition in full, rather than having us guess.
This is a strawman argument, you're arguing semantics here. You're a smart person, so you know exactly what he means. The perception created by your article is that people shouldn't use Go because it's not memory-safe. But the average developer hearing "not memory-safe" thinks of C/C++ level issues, with RCEs everywhere.
Unless you can show a realistic way this could be exploited for RCE in actual programs, you're just making noise. Further down the thread, you admit yourself that you're in a PLT research bubble and it shows.
If you haven't already, I highly recommend reading up on the GBU-57 "bunker buster" bomb, because it is some Merrie Melodies Acme brand munitions. It's deliberately as heavy as they can make a bomb, not with explosives but just with mass. They should have shaped it like a giant piano.
As for the facts, and not just the narrative: 60% enrichment is not considered weapons-grade enrichment, and it is not illegal under the NPT (Nuclear Non-Proliferation Treaty). Therefore, today's attack is an illegal act of aggression against another country, violating international law. Those are the facts.
"I just used o3 to design a distributed scheduler that scales to 1M+ sxchedules a day. It was perfect, and did better than two weeks of thought around the best way to build this."
Anyone with 10 years in distributed systems at FAANG doesn’t need two weeks to design a distributed scheduler handling 1M+ schedules per day, that’s a solved problem in 2025 and basically a joke at that scale. That alone makes this person’s story questionable, and his comment history only adds to the doubt.