Hacker News Reader

Hacker News

Comment by mort96 | Hacker News Reader

Parent Full thread

mort96

And now all your source files contain URLs to abandoned infrastructure. Is that what you'd want long term?

View on HN

It's a solution that keeps you working now and you can do the actual search and replace when scheduling allows.

AKA it solves nothing, just kicks the problem down the road.

welcome to fast moving companies.

How's that any different from java code using package names starting with com.sun?

com.sun is an identifier, nothing more. No tooling sees com.sun and assumes, "oh that means I can make an HTTP request to the IP address which sun.com resolves to".

In Go, the package identifiers are literally URLs. Go's own tooling assumes that it can make an HTTP request to the URL and that the response will be HTML with particular tags which Go's tooling will parse and use to resolve a git repository which can be 'git clone'd. Leaving them as-is when you abandon the infrastructure they reference literally means leaving dead links in your source code.

If it's not fetching from the URL then it's not really a URL, just an identifier that looks like a URL.

What do you mean? Go's tooling definitely tries to fetch from that URL.

Not if you tell it a different URL though

That's just the default, which you can easily override if you need to. IMO there is nothing wrong with treating Go package names as arbitrary identifiers like com.sun.* If you're spending a lot of time updating imports because the underlying repo has moved from its original URL, then just don't do that. It's unnecessary.

And leave URLs to abandoned infrastructure all over the place? No thank you.

Sounds like classic developer OCD to me. Old URLs used as Go package identifiers are completely harmless.

Until your tooling automatically makes a request to a now-untrusted server and trusts its response...

The Go tooling won't do that if you configure it properly (e.g. via a 'replace' directive in your go.mod or https://go.dev/ref/mod#goproxy-protocol)

Any tool that automatically assumes that a URL in a Go module import is 'trusted' is just a broken tool.

And if any tooling ever gets executed without the proper replace directive...

Any tooling that looks at Go module imports should respect the contents of go.mod.

If you haven't added a replace directive to your go.mod, then you certainly haven't replaced all instances of the old URLs with updated ones.

Go mandates lockfiles, called go.sum

Reply on news.ycombinator.com