Are you seriously saying that github.com/somelib is a better package management? Of course nobody forces to use that, but it's what actually been used in most go projects. Even NPM looks better in comparison.
The best quality package management I've seen is Maven, followed by Cargo.
for private Go packages all I need is to point it to another git repo. for nuget/maven etc - I need an artifact registry, with it's own bells and whistles
Location: Ukraine
Remote: Yes
Willing to relocate: Yes, preferably UK/US/Canada
Technologies: Go, AWS, k8s, C#/.Net Core, PostgreSQL, MongoDB.
Résumé/CV: https://suddengunter.github.io/cv
Email: kolomytsev1996@gmail.comWhat Go actually needs: Nil-Safe Types! [1]
Programmers can work around verbose error handling(3) and lack of enums(1), but forget to check for nil before using a pointer... CRASH! And that's something the compiler doesn't warn about.
[1]: https://wakatime.com/blog/48-go-desperately-needs-nil-safe-t...
In C# we were going from "every reference type can be null" to "only things marked with '?' can be null" with nullable reference types. When I started using Go it was nice to see that only something, that is explicitly created as pointer is nullabe, everything else can't be null / nil - and you can't get panic from nil referencing stuff
When a few years ago I moved from Eastern Europe (where I had 1GB/s to my apartment for years) to the UK I was surprised that "the best" internet connection I was able to get was about 40MBit/s phone line. But it's a small town, and during past years even we have fiber up to 2GB/s now.
I'm surprised US still has issues that you mentioned. Have you considered Starlink(fuck Musk, but the product is decent)/alternatives?