Re:The tragedy of running an old Node project
by Aeolun on Tuesday November 19, 2024 @04:05AM
(#42181355)
Every single time I clone anything Go, I first spend a few hours sorting out dependency issues.
[ Parent
| on HN ]
Re:The tragedy of running an old Node project
by segfaltnh on Tuesday November 19, 2024 @07:01AM
(#42182509)
This shocks me, what sort of issues do you hit?
Re:The tragedy of running an old Node project
by fredrikholm on Tuesday November 19, 2024 @07:42AM
(#42182797)
+1 on this. I've been using Go almost exclusively for the last 5 ish years partly because this sort of thing never happens.
Re:The tragedy of running an old Node project
by thrw42A8N on Tuesday November 19, 2024 @08:55AM
(#42183442)
You lucked into the period when they solved the issues. If you need to work with older projects and can't easily convert them, you're going to have a bad time.
Re:The tragedy of running an old Node project
by popcalc on Tuesday November 19, 2024 @09:41AM
(#42183931)
I open up random Go projects from a decade+ ago every week with no issues.
Re:The tragedy of running an old Node project
by thrw42A8N on Tuesday November 19, 2024 @11:02AM
(#42184935)
Lucky you, then. I open them every week too, but definitely not without issues.
Re:The tragedy of running an old Node project
by Aeolun on Tuesday November 19, 2024 @11:10AM
(#42185025)
Mainly weird issues of incompatible dependencies, maybe sometimes something that won’t compile because it’s missing a system dependency? I also feel like it sometimes pulls a newer or older dependency that is the missing some used module.