Avatar
mleku
dff36e5ee6003413b8a6a2615d1712b453c289dee057c90e9416c3cbde553f22
founder of the gopher milk factory https://geyser.fund/project/gophermilkfactory Go and Bitcoin maximalist remnant living in Madeira and working to help the free humans connect with each other.

well, i just have some extraordinary experiences dealing with certain codebases that are funded by certain organisations and these experiences make me wonder how much money is actually going into them, what the culture of those who receive the money to work on them is, because it's sure seems difficult to get fixes merged in without having showed up at a conference to drink beer with them.

seems like it's mainly about marketing. it's a general thing in the world at large... quality things tend to be humbly presented.

πŸ™ it is thankless work too, i'm sure, so just doing my bit.

as a go and bitcoin dev i can tell you stories about how incredibly weird the entire bitcoin funding culture is altogether. most of the money is going to people who are more influencoor than programmer, and certainly, very little at all is going to real engineers and problem solvers.

https://github.com/gin-gonic/autotls

this one happily built an example executable first time in 5 seconds on a machine with 500mb of memory.

almost all of the rest of them require you to include all this crap from azure and alibaba and will burn more than 400mb of memory.

oh, sure, most of us have more than this but WHY BURN RESOURCES FOR NOTHING?

cannae no zap ye laddie

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.

standard japanese toilet usage instructions:

two facts that most english speakers do not know:

goat milk is the most commonly consumed and produced type of milk.

most people have toilets that they squat to poop in.

trad japanese toilet:

i have a rule, if i saw the name on the MSM i estimate that it will be 2 stars out of 10. 1 star if there is two names that i know from MSM.

you should threaten it with a DoS attack and see if it still wants to do that.

humm the screenshot program didn't remove the overlay on the part it snapped