Don't couple your Go code to GitHub

kept by eddie oct 02

The article advises Go developers to avoid hardcoding GitHub dependencies, promoting loose coupling for better portability, reduced vendor lock-in, and easier migration to alternative version control systems.

Package managers keep using Git as a database, it never works out
Using Git as a package manager backend causes performance and scaling problems as ecosystems grow, leading to workarounds like proxies and sparse checkouts.
also on #go, GitHub, #software-engineering, #developer-tools
Poisoning a Go Cache
The post demonstrates how manipulating Go's build cache can alter program behavior without source changes, using overlays and cache poisoning to reverse a function's output from true to false.
also on #go, #programming-languages, #software-engineering, #developer-tools