commit 8a2152624237d1e4abb3ade3eaeae95fef06b6f4
parent d925c6ba83fb7d5be309d0aefc1864fe964a0e6b
Author: decentral1se <decentral1se@web>
Date: Sat, 3 Aug 2024 16:43:12 +0200
hmmm stick with that main point
Diffstat:
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/Go.mdwn b/Go.mdwn
@@ -14,7 +14,4 @@ There are [language design decisions](https://tinygo.org/docs/concepts/faq/why-a
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.
-Similar to [[Rust]], Go has several disadvantages from a permacomputing perspective:
-
-- As mentioned above, there are several antithetical language design decisions which optimise for efficient large-scale operation instead of human-scale comprehensibility
-- Largely dependent on [[Big Tech]] for resources and funding
+Similar to [[Rust]], Go is largely dependent on [[Big Tech]] for resources and funding.
