Earlier quoted context omitted.
When Anthropic said they wouldn't sell LLMs to the government for mass surveillance or autonomous killing machines, and got labeled a supply chain risk as a result, OpenAI told the public they have the same policy as Anthropic while inking a deal with the government that clearly means "actually we will sell you LLMs for mass surveillance or autonomous killing machines but only if you tell us it's legal". If you alrea…
I'm not some kind of OpenAI or Pentagon fanboy, but it's pretty easy to for me to understand why a buyer of a critical technology wants to be free to use it however they want, within the law, and not subject to veto from another entity's political opinions. It sounds perfectly reasonable to me for the military to want to decide its uses of technologies it purchases itself. It's not like the military was specifically…
1M context is now generally available for Opus 4.6 and Sonnet 4.6
271–280 of 565 posts
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#272Earlier quoted context omitted.
I'm not some kind of OpenAI or Pentagon fanboy, but it's pretty easy to for me to understand why a buyer of a critical technology wants to be free to use it however they want, within the law, and not subject to veto from another entity's political opinions. It sounds perfectly reasonable to me for the military to want to decide its uses of technologies it purchases itself. It's not like the military was specifically…
[flagged]
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#273Is there a writeup anywhere on what this means for effective context? I think that many of us have found that even when the context window was 100k tokens the actual usable window was smaller than that. As you got closer to 100k performance degraded substantially. I'm assuming that is still true but what does the curve look like?
> As you got closer to 100k performance degraded substantially In practice, I haven't found this to be the case at all with Claude Code using Opus 4.6. So maybe it's another one of those things that used to be true, and now we all expect it to be true. And of course when we expect something, we'll find it, so any mistakes at 150k context use get attributed to the context, while the same mistake at 50k gets attributed…
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#274Friends, just write the code. It’s not that hard.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#275It’s interesting because my career went from doing higher level language (Python) to lower language (C++ and C). Opus and the like is amazing at Python, honestly sometimes better than me but it does do some really stupid architectural decisions occasionally. But when it comes to embedded stuff, it’s still like a junior engineer. Unsure if that will ever change but I wonder if it’s just the quality and availability of…
I've found it's ok at Rust. I think a lot of existing Rust code is high quality and also the stricter Rust compiler enforces that the output of the LLM is somewhat reasonable.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#276Earlier quoted context omitted.
I'll be more likely to agree with anything being AGI if it doesn't have such obvious and common brittleness. These LLMs all go off the rails when the context window gets large. Their context is also easy to "poison", and so it's better to rollback conversations that went bad rather than trying to steer them back to the light. There's probably more examples, but to me AGI must move beyond the above issues. Though fran…
How are you rolling back a conversation? I didn't know tools exposed that functionality.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#277Earlier quoted context omitted.
Is it ever useful to have a context window that full? I try to keep usage under 40%, or about 80k tokens, to avoid what Dex Horthy calls the dumb zone in his research-plan-implement approach. Works well for me so far. No vibes allowed: https://youtu.be/rmvDxxNubIg?is=adMmmKdVxraYO2yQ
I'd been on Codex for a while and with Codex 5.2 I: 1) No longer found the dumb zone 2) No longer feared compaction Switching to Opus for stupid political reasons, I still have not had the dumb zone - but I'm back to disliking compaction events and so the smaller context window it has, has really hurt. I hope they copy OpenAI's compaction magic soon, but I am also very excited to try the longer context window.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#278compaction has been really good in claude we don't even recognize the switch
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#279Also it is really good for writing SketchUp plugins in ruby. It one shots plugins that are in some versions better then commercial one you can buy online.
CC will change development landscape so much in next year. It is exciting and terrifying in same time.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#280Opus 4.6 is nuts. Everything I throw at it works. Frontend, backend, algorithms—it does not matter. I start with a PRD, ask for a step-by-step plan, and just execute on each step at a time. Sometimes ideas are dumb, but checking and guiding step by step helps it ship working things in hours. It was also the first AI I felt, "Damn, this thing is smarter than me." The other crazy thing is that with today's tech, these…
I am starting to believe it’s not OPUS but developers getting better at using LLMs across the board. And not realizing they are just getting much better at using these tools. I also thought it was OPUS 4.5 (also tested a lot with 4.6) and then in February switched to only using auto mode in the coding IDEs. They do not use OPUS (most of the times), and I’m ending up with a similar result after a very rough learning c…