> terminal UI written in Go

> Linux only

Any particular reason for that? Are you using specific Linux APIs?

Just to clarify, this looks like a super helpful utility, something that I would personally use. The issue is that I noticed the installation instructions include a link to a prebuilt binary hosted on your website. Without providing access to the source code, you're asking users to trust executing an unknown binary on their system.

▲

taskset 2 hours ago | parent [-]

I no longer use GitHub for original projects. Source for fftool isn't public yet but I understand the concern — running an unaudited binary is a real ask. My site leans toward educational, so that people consider building the tool from the instructions in the article. I may host the source on the site as a zip or tarball at some point so people can more easily build it.

As for Linux API - TIOCGWINSZ via syscall.IOCTL to get terminal dimensions.

Why Linux and Go - Linux is the only OS I use. I like Go because it produces a single static binary with no runtime dependencies. Thanks for your interest.

	▲	jbstack an hour ago \| parent \| next [-]
		I don't understand what this comment is trying to say. > ... people consider building the tool from the instructions in the article ... so people can more easily build it So what's the "less easy" way that people can build it from the instructions, if there's no source code?
	▲	lionkor 2 hours ago \| parent \| prev [-]
		You use charmbracelet/bubbletea for the TUI, which does seem to support Windows, what am I missing?