3 ms·
Disclaimer - I worked on this Codex CLI prototype. As someone who's worked on natural language interfaces for years this hits hard. The long tail of ways that
by not_a_bot_ryan 4y ago
Disclaimer - I worked on this Codex CLI prototype.
As someone who's worked on natural language interfaces for years this hits hard. The long tail of ways that people express themselves have always made it near impossible to truly build systems that understand our intent and can act on it. I don't think LLMs are a silver bullet that nullify this, but I do think they're exceptionally better than what we've had in the past and that with the right user interface can help us take strides in the right direction.
In the case of the Codex CLI - the goal isn't to eliminate PowerShell, Bash or zsh as computer interfaces, but to assist developers (new and old) as they're using them. The Codex CLI is using Codex off-the-shelf (no customization), and is already quite capable of helping me handle complex shell tasks that I would have taken me much longer to handle in the past. That it can rely on my NL->Code dialog history also gives it context about my task that StackOverflow could never have.
I think the key here will boil down to the user experience - a UX that eliminates shell languages and just takes natural language would be awful, but one that thoughtfully helps you express yourself in terse languages can be helpful.