There is something really strange about a lot of recent Go projects including this one. I can't put my finger on, but the combination of the author and the type of problem they choose to tackle oftentimes seems baffling to me. Most projects seem to be solving a problem that is often misidentified or otherwise badly solved, but somehow the focus ends up being on the code architecture or the UI design. It's like they're trying to solve a problem just for the sake of writing some code and the correct way to use Go idiomatically or something and don't really care about the problem or how well the solution actually works.