I wonder if this is like when a restaurant introduces a new menu to increase prices. Is Opus 4.7 that significantly different in quality that it should use that much more in tokens? I like Claude and Anthropic a lot, and hope it's just some weird quirk in their tokenizer or whatnot, just seems like something changed in the last few weeks and may be going in a less-value-for-money direction, with not much being said a…
Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
141–150 of 620 posts
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#142Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#143Earlier quoted context omitted.
qwen3.5/3.6 (30B) works well,locally, with opencode
Is this sort of setup tenable on a consumer MBP or similar?
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#144Earlier quoted context omitted.
qwen3.5/3.6 (30B) works well,locally, with opencode
I want to bump this more than just a +1 by recommending everyone try out OpenCode. It can still run on a Codex subscription so you aren’t in fully unfamiliar territory but unlocks a lot of options.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#14545% is brutal if you're building on top of these models as a bootstrapped founder. The unit economics just don't work anymore at that price point for most indie products. What I've been doing is running a dual-model setup — use the cheaper/faster model for the heavy lifting where quality variance doesn't matter much, and only route to the expensive one when the output is customer-facing and quality is non-negotiable.…
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#146I've spent the past 4+ months building an internal multi-agent orchestrator for coding teams. Agents communicate through a coordination protocol we built, and all inter-agent messages plus runtime metrics are logged to a database. Our default topology is a two-agent pair: one implementer and one reviewer. In practice, that usually means Opus writing code and Codex reviewing it. I just finished a 10-hour run with 5 of…
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#147Earlier quoted context omitted.
You can argu that you will have skill atrophy by not using LLMs. We have gone multi cloud disaster recovery on our infrastructure. Something I would not have done yet, had we not had LLMs. I am learning at an incredible rate with LLMs.
> I am learning at an incredible rate with LLMs Could you do it again without the help of an LLM? If no, then can you really claim to have learned anything?
Not everyone learns at the same pace and not everyone has the same fault tolerance threshold. In my experiencd some people are what I call "Japanese learners" perfecting by watching. They will learn with AI but would never do it themselves out of fear of getting something wrong while they understand most of it, others that I call "western learners" will start right away and "get their hands dirty" without much knowledge and also get it wrong right away. Both are valid learning strategies fitting different personalities.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#148And yes, Claude models are generally more fun to use than GPT/Codex. They have a personality. They have an intuition for design/aesthetics. Vibe-coding with them feels like playing a video game. But the result is almost always some version of cutting corners: tests removed to make the suite pass, duplicate code everywhere, wrong abstraction, type safety disabled, hard requirements ignored, etc.
These issues are not resolved in 4.7, no matter what the benchmarks say, and I don't think there is any interest in resolving them.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#149Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#150We dropped Claude. It's pretty clear this is a race to the bottom, and we don't want a hard dependency on another multi-billion dollar company just to write software We'll be keeping an eye on open models (of which we already make good use of). I think that's the way forward. Actually it would be great if everybody would put more focus on open models, perhaps we can come up with something like the "linux/postgres/git…