Golang's dependency management can't be fixed. Cloud vendoring / relying on for stuff was like a secret JavaScript sin but here Go has it out in the open.

What is the deal? I don't want to bust open the internals of this language to see if it's fixable at a deeper level b/c it's non-portable (if I found a way to package artifacts, they'd have to be system-specific) -- so eventually, with my druthers, I'll land on Rust for this kind of thing I guess :/

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!