ryeguy

They can benchmark it because you can use an openai api key with cursor. Astra is just not included in the cursor plan.

What does this question have to do with the linked article?

I keep seeing mention of the cache, what's special about it? All frontier llms have prefix caching, what is special about deepseek's approach?

Openrouter's pricing via the deepseek provider is the same as the official deepseek api for both flash and pro and for cached and uncached tokens. It's literally the same api.

And no, cache rates are not different if you're going through the official deepseek provider. The only way caching rates can drop is if you let openrouter fully control routing by preferring uptime or something, and then it might bounce you between providers. But you can control which providers for a given model are in its routing pool and stop that.

Sure, but they at least quantified it with data. It's not like they just dropped a sentence saying the above, they showed numbers.

Did you read the blog post? They compare to deepswe and call it out as the worst one for false positives (failed, but the benchmark assessed it as correct). It also has less language variance.

This isn't how LLMs work. They aren't self aware like this, they're trained on the general internet. They might have some pointers to documentation for certain cases, but they generally aren't going to have specialized knowledge of themselves embedded within. Claude code has no need to know about its own internal programming, the core loop is just javascript code.

This take sucks. The anticheat software in this context is for competitive games. No one cares about people cheating in isolation in single player games. The anticheat is to stop 1 guy from ruining it for the 9 others he's playing with online.

You can argue about the methods used for anticheat, but your comment here is trying to defend the right to cheat in online games with other people. Just no.

MCP is just function calls with parameters. Whether or not it's push or pull can be decided by the author. A push model takes the scan as an input to the mcp call. A pull model does the pulling within the mcp call. Neither is right or wrong, it's situational.

To me, dabbled means learned the fundamentals of the language but hasn't written real software in it. I would expect a dabbler to have been exposed to class inheritance and primitives such ss symbols.

That makes sense as a general pattern, but probably less so in the context of rails which is typically a self contained monolith. It would be adding another hop, more indirection, and more complexity. It would introduce new problems like the need to segment your "real" api from your worker api for the purpose of load isolation.

How does this reduce operational overhead? You still need a queue and a worker to dispatch the tasks to your api.

Your gemini pricing is for flash, not pro. Also, claude uses prompt caching and gemini currently does not. The pricing isn't super straightforward because of that.

They emailed us in advance of the update being pushed out saying it would lower battery life, and offered compensation options ahead of time. It wasn't reactionary. If it were a buggy update the email wouldn't come before the update.