think about how it would do the same for python/golang/lua/etc.
I would never write a TUI like this and simply `eval` in the same scope as the TUI frames.
you shell out and run it with the language engine required.
Opencode has the ability to lean on LSP and Formatters, but these are not required to be written in the same language as the TUI
think about how it would do the same for python/golang/lua/etc.
I would never write a TUI like this and simply `eval` in the same scope as the TUI frames.
you shell out and run it with the language engine required.
Opencode has the ability to lean on LSP and Formatters, but these are not required to be written in the same language as the TUI