2 ms·
Seems completely in line to me: - go is a broad stdlib langage - go has a bespoke toolchain with little to no hooks, meaning anything which needs to integrate
by masklinn 5y ago
Seems completely in line to me:
- go is a broad stdlib langage
- go has a bespoke toolchain with little to no hooks, meaning anything which needs to integrate directly into the build process or to instrument the runtime benefits extensively from being brought in-tree e.g. profilers, sanitisers, and (guided) fuzzers
- finally go’s “niche” are mainly network daemons and CLI utilities, so lots of interacting with network streams and file processing, which are the main use cases for fuzzing