3 ms·
Agreed but lets keep in mind that graphical UIs involve significantly more effort than CLIs. In the case where you shoerhorn an ai to be your primary UI I would
by theK 3y ago
Agreed but lets keep in mind that graphical UIs involve significantly more effort than CLIs. In the case where you shoerhorn an ai to be your primary UI I would bet this is as hard if not harder since you typically have to code around significant limitations of current llms
- fragmede 3y agohttp://gitwit.dev http://gitwit.dev shows us that LLMs can generate various GUIs just fine, when prompted.
- theK 3y agoThis is not what I said. Sure you can use such tools or even just classical boilerplate scripts (like we used for a decade now) to get started with react fast. But building out a system that fails well when the underlying llm starts behaving erratically or not at all is a completely different league of engineering as executing a boilerplate script.
- fragmede 3y agoSorry for misinterpreting you. So the underlying LLM starts misbehaving, and the difficulty you see, is that the system as a whole should fail gracefully. What would that look like, in your eyes? A proctor LLM/whatever that observes the output and decides that it has gone awry and decides to take over?