In our internal evals and testing, medium effort achieved slightly lower intelligence with significantly less latency for the majority of tasks.

We reverted this change on April 7 after users told us they'd prefer to default to higher intelligence and opt into lower effort for simple tasks.

placing constraints upon them not only helps users and services build trust in them, but it also helps people more easily conceptualise what they do.

when setting up a new Macbook it presents FileVault as an optional checkbox and I can certainly tell you that there are many people (including my younger self and my family member with the Intel Mac) who do not know what it is and choose to disable it instead.

Teams at companies like Notion, Ramp, Braintrust, and Wasmer are already using Codex to accelerate their engineering workflows.

The point of GPL licenses is to protect the user of the software, not the developer. If you want "protection" as a developer, use MIT (disclaimer of warranty). GPL "infects" other parts of a system to combat a work-around which was used to violate the software freedom of the user, by firewalling sections of GPL'ed code from the rest of the system. If you don't care about your users' software freedom in the first place, then (L)GPL is the wrong choice.

What this means is: I better refrain from writing a new book and we rather focus on more and better docs.

Might be a little too low-level (even with GUIs) for some teams of users. GPG and Git both require some setup and experience in these tools, or the willingness to learn. Porting a GPG key from machine to machine is not trivial.