The 4-chan Go programmer
dolthub.com
The 4-chan Go programmer
1–10 of 177 posts
Re: The 4-chan Go programmer
#2A timeless classic from Buena Vista Social Club comes to mind https://www.youtube.com/watch?v=o5cELP06Mik
Re: The 4-chan Go programmer
#3The "chan chan Value" or "chan struct{resp chan Value}" is actually a pattern I've used in a very specific situation. It's a situation where a message bus probably could have been used instead, but then you'd have a message bus to handle...
Re: The 4-chan Go programmer
#4I'm going to post a low-effort, non-substantive comment because I can.
That meme in the first few paragraphs made me actual lol as a recovering C programmer.
That is all.
I love seeing odd contortions of languages like this, and C has opportunity aplenty, interesting to see it in Go.
Re: The 4-chan Go programmer
#5There is a Go developer that defends using channels four times like in this blog, he also made some great medium posts in which he details real use cases.
His name is Christopher, if you want to find more about him, just Google “chris chan 4chan”.
Re: The 4-chan Go programmer
#6There is a Go developer that defends using channels four times like in this blog, he also made some great medium posts in which he details real use cases. His name is Christopher, if you want to find more about him, just Google “chris chan 4chan”.
gottem
Re: The 4-chan Go programmer
#7As a scientist that ends up working closely with actual professional software engineers... lots of the stuff they do looks like this do me, and I can't for the life of me make sense of why you'd do it.
I have seen a single line of code passed through 4 "interface functions" before it is called that call each other sequentially, and are of course in separate files in separate folders.
It makes reading the code to figure out what it does exhausting, and a few levels in you start to wonder if you're even looking at the right area, and if it will ever get to the part where it actually computes something.
Re: The 4-chan Go programmer
#8> There's an old programming joke from back in the days when C and its derivatives dominated the landscape.
We are still living in those days.
Re: The 4-chan Go programmer
#9Fun stuff
Re: The 4-chan Go programmer
#10The closest thing to this I've seen in actual code is BlockingQueue>>, which was used to wait for an element from multiple blocking queues simultaneously, where each element is a list of messages.