[philipkglass]

I remember when I had to wait minutes to get a high resolution image over a dialup connection. When computer and communications hardware advanced enough that I could get 30 high resolution images every second, there were brand new uses. In the case of LLMs, I could imagine that much faster operations allow you to introduce them as parts of systems that need to react to the real world at high speed, like factory equipment. Showing that a model can do the usual LLM tasks at extremely high speed is just a demo proving that the approach works.

[anothereng]

yeah at a very high speed the agent can code the solution when you ask it for something on the go. Imagine it be able to make a feature as fast as a website loads sometime in the future that would feel like magic

[harel]

The example in the video was a generation of a dashboard app of some sort. I can do that with a "normal speed" Claude in a few minutes. The difference is a few minutes. This is compared to a few weeks in old school development time. I don't have a problem with taking it a little "slow" (as in - few minutes) and lending my thought to it rather than just going for fast generation and who knows what's inside. I get your use case, but this is a specialised one, and not the one 90% of people will think of - everyone want that fast app in 12 seconds... Or so it seems from me being downvoted on that comment.

[srdjanr]

I frequently tell agent to do something, wait ~10 min (which is just enough that I can't/don't want to start anything else), ask it to change something, wait a few minutes again, and so on. So I'm basically idle while waiting for agent, and it would be great if it was faster.

It's like your compile times were ~10 min. Sure, it's not a huge deal, but it's sooo anoying

[harel]

10 minutes sounds like a very long time. Maybe I'm using it differently but I don't see those wait times. I give specific instructions, and use pro plans, and the turnaround is fast.