commit 327e50f322096fbd111d6bc31ae873527f81e331
parent dbceb4df6144d6fb4abbe1dbbe708901338f3a8e
Author: decentral1se <decentral1se@web>
Date: Sat, 3 Aug 2024 16:00:37 +0200
link & additional wording
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Go.mdwn b/Go.mdwn
@@ -12,4 +12,4 @@ Go can be [[bootstrapped|bootstrapping]] with Go, or C (via `gccgo`/`gollvm`). H
There are [language design decisions](https://tinygo.org/docs/concepts/faq/why-a-new-compiler/) which make Go unsuitable for embedded systems. The [TinyGo](https://tinygo.org) project aims to provide an alternative.
-Go binary sizes are [generally acknowledged](https://github.com/golang/go/issues/6853) to be "bloated". For example, a binary size of [1.3 MB for 6 lines of code](https://dr-knz.net/go-executable-size-visualization-with-d3.html). The design of Go prioritises performance at the cost of memory, embedding considerable amounts of information in produced binaries. Passing flags such as `-ldflags="-s -w"` to `go build` can aid in size reduction.
+Go binary sizes are [generally acknowledged](https://github.com/golang/go/issues/6853) to be [[bloated|bloat]]. For example, a binary size of [1.3 MB for 6 lines of code](https://dr-knz.net/go-executable-size-visualization-with-d3.html). The design of Go prioritises performance at the cost of memory, embedding considerable amounts of runtime information in produced binaries. Passing flags such as `-ldflags="-s -w"` to `go build` can aid in size reduction.
