I do not really get the point of layouts such as altgr-intl tbh (even without dead keys). It is fine if you want to write here and there the name of a person that includes non-english characters, but I cannot write actual text in that. Whenever I encounter this layout somewhere I just find it annoying even in english, though I guess dead keys is what actually makes it annoying.
Without dead keys it is def better, but even then I cannot write in said non-english language with that, instead of using one actual layout for that language, and I do not see why not just change layout. Granted, there are some small annoyances because punctuation marks may change place, but I find that easier to learn than using altgr to write letters.
If you are on a us ansi keyboard and switch to a iso layout (most European layouts are iso) you have I believe two unreachable keys. And the arrangement of the others is slightly different you will have to adapt your muscle memory anyway.
Altgr-intl is pretty good for when you code and write English most of the time and occasionally need accented letters. If you need to write a lot in your native language it's better to get a local layout keyboard.
With Codex (5.3), the framing is an interactive collaborator: you steer it mid-execution, stay in the loop, course-correct as it works.
With Opus 4.6, the emphasis is the opposite: a more autonomous, agentic, thoughtful system that plans deeply, runs longer, and asks less of the human.
that feels like a reflection of a real split in how people think llm-based coding should work...
some want tight human-in-the-loop control and others want to delegate whole chunks of work and review the result
Interested to see if we eventually see models optimize for those two philosophies and 3rd, 4th, 5th philosophies that will emerge in the coming years.
Maybe it will be less about benchmarks and more about different ideas of what working-with-ai means