In the past, running LLM inference on GPUs was the slowest part of the agentic loop, so API service overhead was easy to hide.

All of these requests can add up to minutes that users spend waiting for Codex to complete complex tasks.

you can short-circuit that by diminishing the experience focusing on a language focusing on a word focusing on a sound or a meaning you miss the experience and you catch a word right and that's that's the whole that's like all of it in a nutshell

Then again that makes little sense when trying to account for why people use the less-standard preventative instead of preventive or irregardless instead of regardless, he notes.

In fact, most people believe that to build a RESTful API you can simply create an API based on URLs and HTTP verbs. This is absolutely false. This misunderstanding is going around for too long.

Historically, the uncertainty principle has been confused[5][6] with a related effect in physics, called the observer effect, which notes that measurements of certain systems cannot be made without affecting the system, that is, without changing something in a system.

Just throwing in <div class="{$$props.class || ''} otherChildClass"></div> seems the easiest, and it'll avoid undefined classes. I feel like many aren't noticing the undefined values getting inserted in their classes.

Common misuse example and how to fix it

A common mistake is to see those escaped angle brackets, and "improve" the helper by making everything html_safe: