goroutine-inspect VS trusearch

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.

These days you can benefit from minilanguages without actually implementing them. It is surprisingly easy to embed JS or Lua into your program.

Recently I was looking for Linux games at some Russian torrent site which match my taste. Search engine on it is not particularly good, it allows search only on torrent title. While each torrent description contains genre, year and a lot of other info which is pretty suitable for machine interpretation.

So I found XML dump of tracker database (about 22 GB) with torrent descriptions and built tool which allows to process torrent records with an arbitrary JS script to filter records. Like AWK, but suited for specific XML input and scripted with JS.

This way I could filter games based on year, genre and gaming engine. JS engine I used is implemented in pure Go, so it doesn't introduced additional runtime dependencies. With such approach it's easy to write any search query, aggregation and so on.

BTW, here is the project link: https://github.com/Snawoot/trusearch