gocui VS Rich Interactive Widgets for Terminal UIs

I've been using the gocui library for building apps that are too small for a full blown server based solution, but still need to capture text input and menu selection.

I've had fun writing an app with https://github.com/rivo/tview.

Spotify-TUI was developed in Rust, therefore I couldn’t simply use the same UI framework. Within Go a popular choice is tview https://github.com/rivo/tview which provides many similar UI widgets which covered all my needs.

. Web backend (with various frameworks available) . Web Assembly (one of them is vugu framework) . Microservices (some frameworks: Go Micro, Go Kit, Gizmo, Kite) . Fragments services (Term mentioned by @jeffotoni in a microservices discussion group) . Lambdas (FaaS example) . Client Server . Terminal applications (using the tview lib) . IoT (some frameworks) . Bots (some here) . Client Applications using Web technology . Desktop using Qt+QML, Native Win Lib (example Qt, Qt widgets, Qml) . Network Applications . Protocol applications . REST Applications . SOAP Applications . GraphQL Applications . RPC Applications . TCP Applications . gRPC Applications . WebSocket Applications . GopherJS (compiles Go to JavaScript)

The jist of what I did: The TUI lib I used was https://github.com/rivo/tview. While technically a TUI, it didn't look like one. Tui gave me components for user input, context-aware output formatting, and configurable hotkeys and command shortcuts. History was just an in-memory string map bound to a hotkey.

tview is built on top of the tcell library mentioned in another comment. I liked it so much that I forked it as cview.

It's tview, the same framework underlying awesome k9s project.

A tui client for WhatsApp. My first ever go project!!! As a very slow learner I am really proud of how far I could bullshit my way through it. I used tview and whatsmeow for this.

After a user request cycle, however, the tview textarea widget is now in active development so stay tuned!