A local tool needs a table, a few charts, and some buttons. Somewhere in the planning meeting, it acquires an entire desktop application.
Before that happens, I want to nominate the browser already sitting on the machine.
I call this Borrowed UI, or BUI : a local process does the work, and a browser tab provides the interface. The established name is a local web UI. The architecture is old. I’m just giving my enthusiasm an acronym.
pprof is the cleanest example. It can print a report of expensive functions, or open a local web interface when a visual inspection helps. Same profiling data, another way to look at it. A graph does not have to become a whole desktop product.
With pprof installed and an existing profile file, its web mode looks like this:
pprof -http=localhost:8080 profile.pb.gz
Graph visualizations can require Graphviz. This is an example of an optional interface, not a promise of zero dependencies. pprof documentation .
Syncthing is the background-service version.…