i just finished building a little NIP-05 tool, and was wondering why the compiler didn't generate a binary.

so i turned on verbose logging (this is go: -a -x) and then this:

github.com/aliyun/alibaba-cloud-sdk-go/services/alidns: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed

this is a little library that is there to get a LetsEncrypt certificate.

signal: killed is a typical way that linux tells you that your compiler just blew your entire system memory. my vps has only got 500mb of memory.

i remember at one stage the Steemit steemd compilation used up more than 16gb of memory and it was impossible to compile on a machine without at least 16gb of memory plus it would also chew up another 8gb of swap.

too few devs have 32gb machines, and don't even realise that their shit blows out this much when compiling.

also, stirfry, i was watching my friend trying to compile it, and after half an hour, the compilation failed on a tagged branch. his laptop is far more equipped than my little old 2020 business laptop.

you all devs need to have some bloody sense when importing things, to be aware of just how much crap you are pulling in along with the stuff that's actually used.

being unable to compile a simple web service app because of an out of memory error is embarrassing for you.

once upon a time, about 5 years ago, hardware would have groaned and probably ground to a halt with the shit you people concoct these days.