i'm programming in Go now it feels like they've mashed the worst parts of C and Javascript syntax together, with the package dependency hell of early-2010s Ruby, and the elitist community of early-2000s Linux fanboys oh, and Google owns it
-
-
you also can't statically link the entire world. eventually you must be dynamically linking, in a sense, to the OS kernel's syscall interface now, on Linux you have Linus who promises to keep that extremely stable, so it works however… Windows and macOS are not Linux.
-
a reasonable individual would conclude, okay, we'll make an exception to dynamically linking just for these OSes, and link to the OS's userland dynamic library that handles kernel stuff and which does have a stable interface however that reasonable individual is not the Go devs
- Show replies
New conversation -
-
-
I'd generally take "linked in and never updated" over dynamically linked against libraries that aren't on the user's system or with versions of libraries that haven't been tested. Has statically linking with the *option* to dynamically link at runtime been tried yet?
-
No, Go always statically links all Go code as far as I know.
End of conversation
New conversation -
-
-
Static compilation is why, for example, trying to build resilient DNS in a datacenter is a royal pain in the ass. There can be dozens of different failure modes on just one host. Use the host's resolver, people! No, not the systemd one...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.