Live data from Hacker News

GPT‑5.3‑Codex‑Spark

openai.com

191–200 of 415 posts

Re: GPT‑5.3‑Codex‑Spark

#191

Earlier quoted context omitted.

Isn't that such a great outcome. No more robotic presentations. The best part is that you can now practice Improv at the comfort of your home.

And this product will work great for any industry... can I get a suggestion for an industry from the crowd? Audience: Transportation... Education... Insurance... Speaker: Great! I heard "Healthcare". Right... as we can see from this slide, this product fits the "Healthcare" industry great because of ...

Caro’s first LBJ biography tells of how the future president became a congressman in Texas in his 20s, by carting around a “claque” of his friends to various stump speeches and having them ask him softball questions and applauding loudly after

Well, hey, who needs friends?

Re: GPT‑5.3‑Codex‑Spark

#192
post #41

I love this! I use coding agents to generate web-based slide decks where “master slides” are just components, and we already have rules + assets to enforce corporate identity. With content + prompts, it’s straightforward to generate a clean, predefined presentation. What I’d really want on top is an “improv mode”: during the talk, I can branch off based on audience questions or small wording changes, and the system p…

You're describing almost verbatim what we're building at Octigen [1]! Happy to provide a demo and/or give you free access to our alpha version already online.

[1] https://octigen.com

Re: GPT‑5.3‑Codex‑Spark

#193
post #111

Earlier quoted context omitted.

By perf I mean how much does it cost to serve 1T model to 1M users at 50 tokens/sec.

All 1T models are not equal. E.g. how many active parameters? what's the native quantization? how long is the max context? Also, it's quite likely that some smaller models in common use are even sub-1T. If your model is light enough, the lower throughput doesn't necessarily hurt you all that much and you can enjoy the lightning-fast speed.

[dead]

Re: GPT‑5.3‑Codex‑Spark

#195

Earlier quoted context omitted.

I routinely leave codex running for a few hours overnight to debug stuff If you have a deterministic unit test that can reproduce the bug through your app front door, but you have no idea how the bug is actually happening, having a coding agent just grind through the slog of sticking debug prints everywhere, testing hypotheses, etc — it's an ideal usecase

I have a hard time understanding how that would work — for me, I typically interface with coding agents through cursor. The flow is like this: ask it something -> it works for a min or two -> I have to verify and fix by asking it again; etc. until we're at a happy place with the code. How do you get it to stop from going down a bad path and never pulling itself out of it? The important role for me, as a SWE, in the p…

I use Codex CLI or Claude Code

I don't even necessarily ask it to fix the bug — just identify the bug

Like if I've made a change that is causing some unit test to fail, it can just run off and figure out where I made an off-by-one error or whatever in my change.

Re: GPT‑5.3‑Codex‑Spark

#196

Earlier quoted context omitted.

> let every part of the market slip away. Which part of the market has slept away, exactly ? Everything you wrote is supposition and extrapolation. Nvidia has a chokehold on the entire market. All other players still exist in the small pockets that Nvidia doesn’t have enough production capacity to serve. And their dev ecosystem is still so far ahead of anyone else. Which providers gets chosen to equip a 100k chips da…

> Nvidia has a chokehold on the entire market. You're obviously not looking at expected forward orders for 2026 and 2027.

I think most estimates have Nvidia at more or less stable share of CoWoS capacity (around 60%), which is ~doubling in '26.

Re: GPT‑5.3‑Codex‑Spark

#197

Earlier quoted context omitted.

> Largest production capacity maybe? Anyone can buy TSMC's output...

Can anyone buy TSMC though?

No. TSMC will not take the risk on allocating capacity to just anyone given the opportunity cost.

Re: GPT‑5.3‑Codex‑Spark

#199
really too bad that the codex models are so tightly coupled to the codex harness as to be useless for everything else

edit: not useless in a absolute sense, but worse than the vanilla gpt models

Re: GPT‑5.3‑Codex‑Spark

#200
post #95

Earlier quoted context omitted.

I have a hard time understanding how that would work — for me, I typically interface with coding agents through cursor. The flow is like this: ask it something -> it works for a min or two -> I have to verify and fix by asking it again; etc. until we're at a happy place with the code. How do you get it to stop from going down a bad path and never pulling itself out of it? The important role for me, as a SWE, in the p…

“here's a failing test—do whatever you can to fix it” Bad idea. It can modify the code that the test passes but everything else is now broken.

I've heard this said a lot but never had this problem. Claude has been decent at debugging tests since 4.0 in my experience (and much better since 4.5)
Post reply on HN