Live data from Hacker News

GPT‑5.3‑Codex‑Spark

openai.com

391–400 of 415 posts

Re: GPT‑5.3‑Codex‑Spark

#391

Earlier quoted context omitted.

Why is the CEO some shady guy? though https://daloopa.com/blog/analyst-pov/cerebras-ipo-red-flags-... "AI" always has some sleazy person behind it for some reason

You need the sleazy person because you need a shit-ton of money.

I have "shady CEO that doesn't give back to his country or community" fatigue

Re: GPT‑5.3‑Codex‑Spark

#392

Earlier quoted context omitted.

How would that compare to subtle bugs introduced by developers? I have seen a massive amount of bugs during my career, many of those introduced by me.

it compares... unfavorably, on the side of ai

Not from what I'm seeing it. 5.3 codex xhigh is pretty amazing.

Re: GPT‑5.3‑Codex‑Spark

#393
post #153

Great move by OpenAI. With coding agents, if you have access to a fast and cheap model, you can afford to let it rip, making lots of mistakes, and iterate until it gets things right. With the right scaffolding (AGENTS.md, SKILLS.md, etc.), a fast and light model can do great things. And when it's done, you can still have the heavyweight model come in to clean up any messes.

Except this thing routinely ignores my AGENTS.md instructions. Very unreliable.

Re: GPT‑5.3‑Codex‑Spark

#394

Earlier quoted context omitted.

The bigger the chip, the worse the yield.

Cerebras has effectively 100% yield on these chips. They have an internal structure made by just repeating the same small modular units over and over again. This means they can just fuse off the broken bits without affecting overall function. It's not like it is with a CPU.

I think what you’re saying is that every wafer is usable, but won’t have the same performance characteristics, depending on how many bits are broken.

Doesn’t that just bucket wafers based on performance? Which effectively gives a yield to each bucket.

Re: GPT‑5.3‑Codex‑Spark

#395

Earlier quoted context omitted.

> 46,255 mm² To be clear: that's the thousandths separator, not the Nordic decimal. It's the size of a cat, not the size of a thumbnail.

This is why space is the only acceptable thousands/grouping separator (a non-breaking space when possible). Avoids any confusion.

The problem is our primitive text representation online. The formatting should be localized but there’s not a number type I can easily insert inline in a text box.

Re: GPT‑5.3‑Codex‑Spark

#396

Earlier quoted context omitted.

I wonder why they named it so similiarly to the normal codex model while it much worse, while cool of course.

Not sure what you mean. It IS the same model, just a smaller version of it. And gpt-5.3-codex is a smaller version of gpt-5.3 trained more on code and agentic tasks. Their naming has been pretty consistent since gpt-5. For example, gpt-5.1-codex-max > gpt-5.1-codex > gpt-5.1-codex-mini.

how are you so sure :)

Re: GPT‑5.3‑Codex‑Spark

#398
post #380

Earlier quoted context omitted.

A competing format that is understandable to probably everybody. An ISO 8601 date is also comprehensible to anybody even if they never seen it before and have to figure it out themselves.

Comprehensible? https://ijmacd.github.io/rfc3339-iso8601/

I said date. Not time, not timestamp, not period, not week, not range, not ordinal date.

Just date.

Post reply on HN