Continue to believe that Cerebras is one of the most underrated companies of our time. It's a dinner-plate sized chip. It actually works. It's actually much faster than anything else for real workloads. Amazing
GPT‑5.3‑Codex‑Spark
81–90 of 415 posts
Re: GPT‑5.3‑Codex‑Spark
#82Why are they obscuring the price? It must be outrageously expensive.
Re: GPT‑5.3‑Codex‑Spark
#83I 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…
Re: GPT‑5.3‑Codex‑Spark
#84Continue to believe that Cerebras is one of the most underrated companies of our time. It's a dinner-plate sized chip. It actually works. It's actually much faster than anything else for real workloads. Amazing
Their only chance is an aquihire, but nvidia just spent $20b on groq instead. Dead man walking.
Re: GPT‑5.3‑Codex‑Spark
#85Earlier 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…
Re: GPT‑5.3‑Codex‑Spark
#86Re: GPT‑5.3‑Codex‑Spark
#87> Our latest frontier models have shown particular strengths in their ability to do long-running tasks, working autonomously for hours, days or weeks without intervention. I have yet to see this (produce anything actually useful).
Re: GPT‑5.3‑Codex‑Spark
#88Earlier quoted context omitted.
This is nonsense what do you mean? Mistral uses Cerebras for their LLMs as well. [0] It's certainly not "untested". [0] https://www.cerebras.ai/blog/mistral-le-chat
Tested at Mistral’s scale is a very different thing to tested at OpenAI’s scale.
So labelling it "untested" even at Meta's scale as a customer (which exceeds OpenAI's scale) is quiet nonsensical and frankly an uninformed take.
[0] https://www.cerebras.ai/customer-spotlights/meta
[1] https://www.cerebras.ai/news/hugging-face-partners-with-cere...
[2] https://www.cerebras.ai/press-release/cerebras-powers-perple...
Re: GPT‑5.3‑Codex‑Spark
#89Continue to believe that Cerebras is one of the most underrated companies of our time. It's a dinner-plate sized chip. It actually works. It's actually much faster than anything else for real workloads. Amazing
Not for what they are using it for. It is $1m+/chip and they can fit 1 of them in a rack. Rack space in DC's is a premium asset. The density isn't there. AI models need tons of memory (this product annoucement is case in point) and they don't have it, nor do they have a way to get it since they are last in line at the fabs. Their only chance is an aquihire, but nvidia just spent $20b on groq instead. Dead man walking…
Re: GPT‑5.3‑Codex‑Spark
#90Earlier quoted context omitted.
Not for what they are using it for. It is $1m+/chip and they can fit 1 of them in a rack. Rack space in DC's is a premium asset. The density isn't there. AI models need tons of memory (this product annoucement is case in point) and they don't have it, nor do they have a way to get it since they are last in line at the fabs. Their only chance is an aquihire, but nvidia just spent $20b on groq instead. Dead man walking…
The real question is what’s their perf/dollar vs nvidia?