[stephc_int13]

Really nice design.

I like CLI and TUI, they can be both practical and aesthetically pleasing, in my opinion the "beauty" of tools is something that can improve the quality of life for the end-user.

But I have a few negative remarks.

- The glow.exe app on Windows is 19M, the launch is fast and I love that it is self contained and portable, but I think that even a pretty markdown viewer could be compiled to a much smaller binary, like easily 10x smaller without doing hardcore demoscene style binary compaction.

- I looked at the examples and source code of some simple widgets like the spinner or the progress bar, I am not fond of the API, too scattered and quite verbose, here again I think that the exact same thing could be written with 1/3 or half the lines without being more difficult to read.

[marcus_holmes]

Go produces large binaries (15Mb+) by default (it optimises for startup time not storage space). There are options to reduce this, but they involve tradeoffs so here be dragons.

Go code tends to be verbose (if you come from a more succinct language). Again, this is a result of design choices made by the Go language designers: optimising for simplicity and explicitness (lack of magic).

I've been coding in Go for years, and find it incredibly readable compared to other languages. I now find less-verbose code harder to read.

[epage]

> The glow.exe app on Windows is 19M, the launch is fast and I love that it is self contained and portable, but I think that even a pretty markdown viewer could be compiled to a much smaller binary, like easily 10x smaller without doing hardcore demoscene style binary compaction.

I've not dug into it but syntax highlighting for code fences probably is costing some space for the syntax definitions.

[bojo]

That binary size is due to the Go runtime also being compiled into it.