permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 9d69bb12e33fe530df70209e55f6027130aed42d
parent 327e50f322096fbd111d6bc31ae873527f81e331
Author: decentral1se <decentral1se@web>
Date:   Sat,  3 Aug 2024 16:22:38 +0200

wording & link

Diffstat:
MGo.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Go.mdwn b/Go.mdwn @@ -8,7 +8,7 @@ Go has a published [language specification](https://go.dev/ref/spec) and a [v1 c The loading of program dependencies is based on URLs. This implies always-on internet connectivity and typically centralised git repository hosting. A work-around for this is to use [vendoring](https://go.dev/ref/mod#vendoring) which supports downloading and bundling all program dependencies into the source tree. -Go can be [[bootstrapped|bootstrapping]] with Go, or C (via `gccgo`/`gollvm`). However, with the introduction of generics, not all new version of Go can be bootstrapped with C. `gccgo` supports [up to 1.18](https://go.dev/doc/install/gccgo). This may be a useful version to target when considering compatibility with unported systems. +Go can be [[bootstrapped|bootstrapping]] with Go itself, or [[C]] (via `gccgo`/`gollvm`). However, with the introduction of generics, not all new version of Go can be bootstrapped with C. `gccgo` supports [up to 1.18](https://go.dev/doc/install/gccgo). This may be a useful version to target when considering compatibility with unported systems. 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.