3 ms·
> these tools are engaging only at the level of text Couldn't we say the same thing about almost all UNIX/Linux coreutils? There's no way to get a strongly-typ
by delta_p_delta_x 3y ago
> these tools are engaging only at the level of text
Couldn't we say the same thing about almost all UNIX/Linux coreutils? There's no way to get a strongly-typed array/tree of folders, files, and metadata from `ls`; it has to be awk-ed and sed-ed into compliance. There's no way to get a strongly-typed dictionary of command-line options and what they do for pretty much every coreutil; you have to invoke `something --help` and then awk/sed that output again.
These coreutils are at their core, only stringly-typed, which makes life more difficult than it strictly needs to be.
Everything is a bag of bytes, or a stream to be manipulated. This philosophy simply leaked into LLMs.
- PoignardAzur 3y agoI think GP's point is we could get much better results if we fed the LLMs with more than the input text. It could still be text, or at least bytestreams: program traces, OpenTelemetry logs, objdump of the compiled binaries, LLVM IR dumps, compiler errors, syntax highlighting markers, etc.
- sanderjd 3y agoThis is, indeed, also a weakness of those tools.