Tootfinder

Another day, another instance of trying to use some #golang code I found on the Internet throwing a nil pointer dereference panic, another moment spent wondering why you would design a language where that is possible in the 21st century

Lies we tell ourselves to keep using #Golang
https://fasterthanli.me/articles/lies-we-tell-ourselves-to-keep-using-golang

As much as I like to hate on #VibeCoding and #LLM s , #claude code helped me ship a bunch of fixes in a #golang codebase I was totally unfamiliar with, within a few hours. I guess it's a case of having the proper experience to steer the tool in the right direction and avoid hallucinations. A power hammer in the hands of an experienced programmer, a rubber hammer in the hands of a novice.

They: Your Go program eats all our memory
Me: checking it eats 22GB of my 32GB in a moment
Me: sync.Pool be it
Me: memory is now around 150MB - but the code has a new constraints
You can read from []byte, you can't store it. Sadly this can't be expressed in Go at all.
#go #golang

#kotlin is #functionalProgramming s biggest success and it did it by copying expressions not pure function purism, xkcd.com/1312 anyone xD
Not to mention Dart style nullish ? that #golang