The only interesting thing is whether OpenCode is more effective at writing code with it's reduced system prompt.

We achieved significant savings simply by moving everything that varies across individuals out of the system prompt so every session starts from a cache point.

For example you never want your system prompt to start with the time that the session started. Move that to the first user message if needed.

The issue with any AI writing is that it all sounds the same.

Once that stops being true, maybe it will be acceptable. But until then, you are left with repetitive crap. That you must wade through. Not good.

If this succeeds, there is no stopping AI given it will have crossed the rubicon of human bottlenecks.

“Hell no”

> “Umm…”

> The problem: CSS can compute a number – 0 for visible and 1 for hidden – but you can’t directly use that number to set visibility. There is a new feature coming to CSS that solves this: if(), but right now it only just shipped in Chrome.

> So I used a trick called type grinding. You create a paused animation that toggles visibility between visible and hidden. Then you set the animation-delay based on the computed value to determine which keyframe is used:

  animation: cull-toggle 1s step-end paused;
  animation-delay: calc(var(--cull-outside) \* -0.5s);

  @keyframes cull-toggle {
    0%, 49.9% { visibility: visible; }
    50%, 100% { visibility: hidden; }
  }

All the background capability Claude code now has makes things way more complex and I saw a meaningful improvement with 4.6 versus 4.5, so imagine other harnesses will take time to catch up.

Apple and Google do same thing with their silly forums.