This is based on what we measure from the API - we see different endpoints depending on how they are served can have different cache hit rates (cache hit rate is defined as the % of cacheable tokens that actually come back as cache hits)
White-throated sparrows across Canada are rapidly replacing their classic three-note song ending with a new two-note version, which originated in British Columbia and has spread eastward over the past two decades.
The whole page reads like it was vibe-written by an AI. If I'd built something as disruptive as this claims to be, I'd have spent at least fifteen minutes writing the announcement myself.
Every time I see 'we' in an announcement like this, I picture one guy alone in his basement.
I think that providing modern monitors that make sense is probably the easiest way to please employees. No matter how excellent the salary is, if they are stuck working on old, small, blurry, faded screens, they'll be unhappy. It also gives a bad impression of the company as a whole. I did L1 tech support a long time ago, and people were overwhelmingly happy to see me coming to replace their old CRTs with LCDs.
I'm thinking super long context length or something to that effect.
I can imagine schemes for instance where context is compressed into chunks and then chunks that are ranked highly relevant for the token are decompressed. Which would sort of be between a long context and a memory retrieval scheme...
Maybe they are doing it on purpose to demonstrate what it looks like when untrustworthy parties have access to frontier llm and that its development should be regulated to protect all of us. /tinfoil
It ought to be extremely easy now to use LLMs to transpile cobol and do the necessary reverse engineering to migrate off mainframes and aix servers.
I think IBM will lose many customers.
It ought to be extremely easy now to use LLMs to transpile cobol and do the necessary reverse engineering to migrate off mainframes and aix servers. I think IBM will lose many customers.
The problem is that those COBOL systems have to be absolutely provably correct, for both financial and regulatory reasons. LLMs can't do that. They're designed to be variable.
You can't vibe code a bank transaction system. "Close enough" isn't good enough in some fields. A minor glitch in a video game may result in screen artifacts. A minor glitch in a banking system can crash the economy.
reply