408 karma · joined December 12, 2010
[ my public key: https://keybase.io/anacrolix; my proof: https://keybase.io/anacrolix/sigs/kUK6TgSm1j2aqELh40B8-WDAv4EeekY8_Us1cbSkS_U ]
The whole system is rigged. Yes, crypto too.
Despite all that I'm a huge fan, and I think Linux support is great
BitTorrent DHT which people don't even realise is there is how it should be
The lure to use channels is too strong for new users.
The nil and various strange shapes of channel methods aren't really a problem they're just hard for newbs.
Channels in Go should really only be used for signalling, and only if you intend to use a select. They can also act as reducers, fan out in certain cases. Very often in those cases you have a very specific buffer size, and you're still only using them to avoid adding extra goroutines and reverting to pure signalling.
If CloudFlare, any "relay" were compromised, all traffic through that would be compromised. That's everything. All your bank details, full access, it's all right there.
The selling point of SSL is nobody can read what you do between you and the final destination, except when the developers of that destination enlist CloudFlare who have a root certificate that allows them to intercept everything whether you realise or not.
Try implementing what CloudFlare does yourself. You will very quickly realise how it works. It's actually pretty crazy.
People don't realise CloudFlare is a MitM-as-a-Service.
Blockchain and DHT are perfect for this.
The frustrating thing is it locks the IO system, but the kernel thinks everything is fine. One by one each thread that does IO never returns. So you frantically click around wondering why your computer isn't doing anything.