cellularmitosis

A YouTuber by the name of Codacus has been pushing the envelope in this area.

I found figma’s remote MCP to be a poor fit for iOS development (it sets tokens on fire and gives Claude the details as React+Tailwind) and got much better results by having Claude build a set of “lens” tools around their REST API (“give me all of the fonts”, “give me the layout dimensions”, “give me the colors”, etc).

The key to making it token efficient was allowing Claude to invent its own plaintext markup format for the lens output.

We don’t know what quantization level was used for the weights or the kv cache for you or for parent poster, so this is probably an apples to oranges comparison.

Maybe switching effort routes you to a different rack of gpu’s which don’t have the cache

The simplest version of this is to just tell two sessions to coordinate by taking turns appending to a markdown file.

Any chance you can throw lzop into that table just as a reference point?

Klipsch was famous for making speakers using acoustic horns, which was somewhat esoteric. When they finally made a speaker which used a conventional woofer, they named it “the heresy”.

A 3dfx card running in an O2 surely deserves a similar moniker :)

Any fans of retrocomputing will certainly agree. Much of the plain-HTTP internet that's left is there by them and for them.

Can you elaborate on “no way back”?

I would guess that most folks would consider a bunch of problem prompts with no reference solutions to be not so useful. How would you check your understanding? How would you know if you were writing go code which would be frowned upon by industry veterans?