I think it's bad for comments in code. If you have the full URL you could at least try to find an archived version for it on archive.org if the link shortener went away.
The archive.org link should be used in code comments imho. This ensures that the content in question has been archived, and points to the temporal snapshot.
Couldn't archive.org go away some day though? It could disappear before the original site. This seems unlikely but it's possible.
I'd rather link to the original but save it on archive.org as a backup. Of course whoever uses the broken link would have to know to go look it up on archive.org.
Well that's always a possibility. The archive.org URL usually contains the full original URL so there's no downside of using it.
In this case though, it's still just code documentation so ideally it should be somewhat possible to figure out what's going on without a link to an external site. It's just about minimizing the risk.
Comments
It's good for comments in code, and back in the old days of twitter before they added in native support for url's in tweets
I think it's bad for comments in code. If you have the full URL you could at least try to find an archived version for it on archive.org if the link shortener went away.
The archive.org link should be used in code comments imho. This ensures that the content in question has been archived, and points to the temporal snapshot.
Even that isn't a guarantee though, as the owner of a URL can request it to be taken down/unindexed.
Couldn't archive.org go away some day though? It could disappear before the original site. This seems unlikely but it's possible.
I'd rather link to the original but save it on archive.org as a backup. Of course whoever uses the broken link would have to know to go look it up on archive.org.
I guess it's a question of minimizing risks and it seems likely that
risk of shorturl site going away > risk of website going away > risk of archive.org going away
Well that's always a possibility. The archive.org URL usually contains the full original URL so there's no downside of using it.
In this case though, it's still just code documentation so ideally it should be somewhat possible to figure out what's going on without a link to an external site. It's just about minimizing the risk.