Discofork
Repository brief

golang/go

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:10:12.397Z
3mo ago

golang/go

golang/go is the upstream repository for the Go programming language, a large, active, non-archived project with very high adoption and frequent recent commits. It is primarily the language and standard toolchain source tree, with top-level areas for API, documentation, library code, miscellaneous support files, source code, and tests.

GitHub
Loading tags...
Stars133,195
Forks18,883
Default branchmaster
Last pushed2026-03-28T20:08:02Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Choose this fork only if profiler-oriented toolchain changes are the goal. For general Go development, production builds, or staying current with upstream, the fork looks too stale and too divergent to be the safer default.

Choose this fork only if Windows 7 support is a hard requirement. If you want current Go features, fixes, and upstream compatibility, the main `golang/go` tree is the better default.

Choose this fork if your primary goal is bare-metal Go on embedded targets and you want built-in no-OS/runtime adaptations. Prefer upstream Go if you need broad platform compatibility, fast access to the latest toolchain changes, or minimal maintenance overhead.

Prefer this fork only if you need the IBM LinuxONE/s390x-specific porting work and are willing to live on an old, highly diverged Go base. For general Go development, current upstream is the better choice by a wide margin.

Choose this fork if your priority is specialized scientific/mathematics-oriented Go behavior and you are comfortable carrying a materially divergent toolchain. Stick with upstream if you need the latest Go releases, easiest maintenance, or maximum compatibility.

Prefer upstream Go unless you specifically need this fork's compiler/codegen experimentation. This fork looks valuable for backend specialization, but its age and divergence make it a poor default for general adoption.