My Go Executable Files Are Still Getting Larger (What's New in 2021 and Go 1.16)

1. shotizam

   1 2 610 5.1 Go

   Shotizam analyzes the size of Go binaries

   

   To promote my own tool, https://github.com/bradfitz/shotizam lets you drill down into why Go binaries are large without having to make up terms like "dark bytes".

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. go

   2 2,237 126,590 10.0 Go

   The Go programming language

   

   one mentioning their findings, but don't quote me on that.

   [1]: https://github.com/golang/go/issues/6853

4. bloaty

   3 15 4,956 6.8 C++

   Bloaty: a size profiler for binaries

   

5. TinyGo

   4 105 15,992 9.6 Go

   Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.

   

   There are go variants for this. See tinygo [1], which targeted embedded originally (iirc) but now also targets wasm.

   So you’re definitely correct that core Go is not an option, but options exist within the “greater metropolitan area” that’s built up around downtown.

   These are among the benefits of having a relatively simple language and a 1.0 compatibility commitment, I think.

   [1]: https://tinygo.org/ their FAQ is quite good.

Suggest a related project