Hello, So the TL;DR is Go packaging is currently a mess. I have realised a reoccurring theme with newer programming languages, everything is static linked creating huge binaries, and none of it is easy to package. Dynamic linking allows for dependency reuse. But for some reason Stack Overflow is flooded with warnings about "don't dynamic link because its less secure". I am far from an expert in linking but I thought that dynamic linking would be more secure because of address space randomisation, which I do not think can be replicated when all the libraries are statically linked into the executable and thus loaded into the same address space, correct me if I am wrong. The issue with static linking and modern languages is they all want to use their own package managers, I have had a few rust devs tell me to "stop packaging their applications because arch users should simply learn to use cargo install". The world is moving away from distribution packages, the time where storage space was limited and expensive is gone and therefore things will continue to become heavier and heavier for convenience. I assume the only time we should package go libraries, or libraries of any modern programming language is, in the off chance, they are dynamically linked against, or the library spits out a shared object? Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev