this is the most stuttering, insane bullshit example of bad programming symbol naming i have ever seen in my life

every single one of those 15 word long symbols has a one, two or three repeating words for no reason and no logic

but yeah, sometimes you come across stuff that fills up a full 2k display, and then you close that file, carefully, back away from teh computer and throw yourself off a cliff

i dare you to try and read the symbol names in this snippet of code

hello darkness my old friend

OMG double bottom. if we break throug these orders ...

... then we are still in this giant range and nothing intersting is going to happen.

stack sats.

Isn’t it funny how the self-proclaimed “liberal” governments who warn about the “dangers of rising authoritarianism” are in fact the authoritarians?

I don't think anyone goes out of their way to travel or be out around people when they are sick without good reason.

The only thing I am concerned with is what are you going to do about it? Being quietly pissed off is your own personal issue, sit & stew if that is what you want to do. But being mad at people for something that I am sure they didn't do on purpose seems pretty fucking self centered.

haha yeah... i refused to use modules for a whole year, they were buggy af lol

now, idk how we'd survive without it but i'm not sure they did it quite perfect, i still keep a GOPATH as a convenient way to organise all my repos

but it works!

there's some glitches here and there with dependencies sometimes though... the btcd and lnd repos notably are a shitfight of dependencies literally back to different versions of the same fucking repo, it's madness

I see u

My global feed is actually so good now using WoT relay this is elite shit

yeah they declined it, it's something you can dig out of the golangnuts mailing list from at least 5 years ago, they just don't see the point of adding this feature to the compiler because of the dramatic computation cost

It’s only a 2x from here and we are back at $100k. Let’s f* go!

yeah, performance optimization is the big cost with funcitonal languages, be it tail recursion or unfolding recursive stuff... recursion is very popular with functional languages but it has its own particular problems, i feel like the Go Authors have declined to add tail recursion to the language because the same logic is more efficiently expressed with for and switch and using concurrent channels and coroutines

wait what? go doesn't have tail call recursion, does it?