2 ms·
Jeez. That golang bug is pretty bad. I'd like to know why it seems that the devs are acting like it's a difficult problem to solve; clearly I'm missing somethin
by simoncion 11y ago
Jeez. That golang bug is pretty bad. I'd like to know why it seems that the devs are acting like it's a difficult problem to solve; clearly I'm missing something.
But, uh, the presence of that bug doesn't invalidate my statement. IPv6 support works out of the box in Go and -if you're on a dual-stack host-[0] everything works great!
[0] So, if you're like not on a cell network with a modern smartphone, or like in an area served by APNIC [1], you're fine! ;)
[1] Because, like, pff, how many people could be served by the networks numbered by that organization? ;)
- hobarrera 11y agoI've a pure-IPv6 setup with NAT64. No golang application works, on any of my machines. This bug is so incredibly critical is actually means that almost every program that depends on golang will not work on any of my machines, or any new machine added to my network.
- simoncion 11y agoHeh. I guess the gonuts [0] are okay with golang not being used on smartphones, in Asia-Pacific, or in Africa. 'Tis a pity. Can you tell me why the golang folks are acting like solving the underlying problem is so terribly difficult? [0] To the downvoters: golang-nuts is the name of the official golang general discussion list. "gonuts" is used lovingly in this context.
- hobarrera 11y ago> Heh. I guess the gonuts [0] are okay with golang not being used on smartphones, in Asia-Pacific, or in Africa. 'Tis a pity. The issue si reproducible on any device, not just smartphones. I hit it constantly on ArchLinux/amd64.
- simoncion 11y agoI know. I apologize for letting my glibness overwhelm my ability to write clearly.