Implicated

About 6 months ago I embarked upon building a little mac native app to monitor all my claude code sessions and alert me/surface sessions that were going to go stale so I could go ping them if I wanted to keep things cached. I named it CREAM.

That eventually grew into what is now my 'software factory' and I've realized, eventually, it's still C.R.E.A.M. (I named it flower) but it's _context_ rules everything around me.

> Even then, 170GB/s is a bump up from 153GB/s of the M5. So we see a 11% uplift already.

My M2 Pro does 200GB/s.

wtf are we even talking about here.

I literally launched my development and web career on the back of this service as a broke early-20s person. Just seeing that link on HN gave me goosebumps. <3

Ask claude to do it end to end, then write a solution that fits your needs from it's experience with you driving it.

I did exactly this - probably the single most valuable piece of software I've "written". It's the backbone of every piece of code coming out of any agent under my control (via MCP toolset).

Knives are dangerous.

> But, my biggest annoyance with most non-flash model providers - including GLM is they will dumb down the models based on load (like switching a non-flash model to flash model).

Where are you seeing this? This would be sufficient for me to stop using that provider entirely, immediately.

seems like maybe we're all just not as mature as you, unfortunate for you.

> not to clone someone else's work and release it for less money.

... You're saying this about _deepseek_?

When I read things like this all I can imagine is a farmer responding in a similar fashion to people talking about using tractors.

I picked up a pre-ai-price-insanity AX162-R at Hetzner a while back and loaded it up on memory to max out the 12 channels the 48c EPYC 9454P as a "this will be the last mysql box I'll need" and have I been _wildly_ impressed with it's performance. The things I throw at it are honestly laughable at times, wildly irresponsible queries against a rather large database, the redis qps metrics are ridiculous and I just load it up with random ggufs since the memory bandwidth is... not terrible and 384GB of it is... useful.

The web app that's hosted on it deals with lots of images and text - over 100mil of each deduplicated, embedded, simhashed - it does the hashing, and the embedding in real time during ingest. Just handles it.

These things are absolutely insane.

> I did not personally test the open weight models beyond the old Qwen 3.6 27B, which produced unusably bad results for me.

So you don't have much perspective on things, it seems. Let me introduce you to the GLM 5.2 and then 5.3/5.3 flash series of... "oh, wow, I should have bought some RTX PRO 6000's while they were 'cheap'" stage of progression.

As someone carrying multiple max subscriptions to both claude and codex - primary workhorse is glm 5.3 flash running on rented GPUs for less than a latte/hr.

I also found qwen 3.6 27B nearly useless for my own needs. DS4 flash 0731 and then 4.1 have been nearly as eye opening as glm 5.3 flash, but have their own warts.

I don't have a horse in this race but I would question the idea that a municipal service has a better reliability record than x/twitter.

> Sol is so much better than Fable 5.

... looks around ...

I think you're arguing the same general point that the person you're responding to is. But you're saying he's not understanding - he understands that they report a cache hit % but you can't look at that public metric with any level of accuracy _because_ most people aren't pinning their providers and they _are_ getting juggled around which is bringing that metric down. That's not to say that specific providers might have issues or worse cache implementations - but it stands that if openrouter is juggling the requests back and forth by default then _that alone_ is breaking caches on those requests in huge numbers.