News for hackers. Stuff that matters.
Re:Mercury 3: Diffusion at scale by cubefox on Monday October 19, 2026 @02:36PM (#50156140)
I have trouble thinking of tasks that "require" this kind of speed. The usual trade-off is between price and quality/reliability.
Re:Mercury 3: Diffusion at scale by krooost on Monday October 19, 2026 @02:50PM (#50156322)
Speed matters most when people are waiting for a response, when information loses value by the second, or when agents make dozens of calls to complete a task.

Customers are already using Mercury 3 for browser use agents, interactive education, real-time search agents, customer support, and more.

Re:Mercury 3: Diffusion at scale by moecables on Monday October 19, 2026 @03:51PM (#50157190)
in my case, I'm hoping that the time-to-first-token isn't so bad that I can have my admin users parse some information in the web ui pretty quickly (a very specific use case, i know)
Re:Mercury 3: Diffusion at scale by dgellow on Monday October 19, 2026 @05:07PM (#50158093)
The time isn’t too relevant for let’s say coding tasks. But if you’re doing user facing, or processing live-data (logs for example) the speed becomes important
Re:Mercury 3: Diffusion at scale by svachalek on Monday October 19, 2026 @08:05PM (#50159653)
It's not really all that fast, for most things it's full seconds or at least a significant portion of a second. As computing goes that's quite slow and there are many things that require much faster speeds than this. However compared to the typical LLM it's quite speedy and opens some new doors for real-time-ish scenarios.