3 ms·

ffmpeg with disposable or llm backed dnd interfaces. for certain types of tooling UIs should be cheap, disposable and task/worlflow specific.

throwaway173738 1y ago
Actually I think this is a killer use case for local LLMs. We could finally get back to asking the computer to do something without having to learn how to string 14 different commands together to do it.
- multjoy 1y ago
  I’ve been computer touching since the mid eighties. Exactly what golden era of computing are you harking back to, and what are you doing that requires 14 different commands?
  - throwaway173738 1y ago
    Linux shells, and that was an exaggeration. The shell is about as general purpose as it gets, but it’s hard to know a priori how to do a certain use case. But if you can explain it in plain language the LLM can do that for you. And at that point maybe you don’t need a gui except to present and manipulate visual output of the shell.
jraph 1y ago
The last thing we want for a user-friendly interface is nondeterminism. Some procedure that works today must work tomorrow if it looks like you can repeat it. LLMs can't be the answer to this. And if you go to the lengths of making the llm deterministic, with tests and all, you might as well code the thing once and for all and not ship the local llm to the end user at all.
- fellowniusmonk 1y ago
  Sorry, I see how my post lacked sufficient clarity. The idea behind a cheap UI is not constant change, but that you have a shared engine and "app" per activity. The particular workflow/ui doesn't need to ever change, it's more of a app/brand per activity for non-power users. This is similar to how some apps historically (very roughly lotus notes springs to mind) are a single app but have an email interface/icon to click, or contacts, or calendar, all one underlying app but different ui entry points.

throwaway173738 1y ago

Actually I think this is a killer use case for local LLMs. We could finally get back to asking the computer to do something without having to learn how to string 14 different commands together to do it.

multjoy 1y ago
I’ve been computer touching since the mid eighties. Exactly what golden era of computing are you harking back to, and what are you doing that requires 14 different commands?
- throwaway173738 1y ago
  Linux shells, and that was an exaggeration. The shell is about as general purpose as it gets, but it’s hard to know a priori how to do a certain use case. But if you can explain it in plain language the LLM can do that for you. And at that point maybe you don’t need a gui except to present and manipulate visual output of the shell.

jraph 1y ago

The last thing we want for a user-friendly interface is nondeterminism. Some procedure that works today must work tomorrow if it looks like you can repeat it. LLMs can't be the answer to this. And if you go to the lengths of making the llm deterministic, with tests and all, you might as well code the thing once and for all and not ship the local llm to the end user at all.

fellowniusmonk 1y ago
Sorry, I see how my post lacked sufficient clarity. The idea behind a cheap UI is not constant change, but that you have a shared engine and "app" per activity. The particular workflow/ui doesn't need to ever change, it's more of a app/brand per activity for non-power users. This is similar to how some apps historically (very roughly lotus notes springs to mind) are a single app but have an email interface/icon to click, or contacts, or calendar, all one underlying app but different ui entry points.