goroutine-inspect VS giu

That's an interesting application. I tend to use an IDE if I'm debugging in realtime and otherwise I'm getting stackdumps from the support org.

For CLI goroutine analysis there's another tool: https://github.com/linuxerwang/goroutine-inspect which is pretty good.

I think if I do a rewrite it might make more sense to go the web route, like the go tool pprof UIs.

[https://github.com/allendang/giu

I prefer giu + zenity for tooling GUIs with either very few or very many elements (i.e. 100's). I use Flutter for when I want an attractive GUI of medium complexity.

FYI, they're using Dear ImGui. Either https://github.com/AllenDang/giu or https://github.com/inkyblackness/imgui-go

I did poke around for a bit, but I really needed the tool, and I knew it would be days of work if I learned a new tool and hours if I stuck with what I knew.

My coworker Andrew did start a similar tool, which is here: https://github.com/andrewpmartinez/grid and uses https://github.com/AllenDang/giu for the UI.

Next time I need a feature I probably take a look at that and see what the model looks like and and how straightforward it is to work with.

To maintain my another GUI lib giu (https://github.com/AllenDang/giu), I used to update imgui manually time to time, and it always a pain in my ass.

I then used GIU (https://github.com/AllenDang/giu) which is a Go wrapper around IMGUI - I found major performance issues since my requirements are pretty extreme, I was plotting charts containing 1000's of points and the overhead of calling the underlying C libraries from Go was too much.