News for hackers. Stuff that matters.
Re:Go hits the concurrency nail on the head by Matthias247 on Thursday October 04, 2018 @07:39PM (#18144586)
True! Haven't thought about it, but it's actually an OS-backed untyped channel, which even supports select().

Guess the differences are: It operates on bytes and not on objects, so a custom protocol is needed on top of it. And it can't provide the same guarantees as an unbounded channel, where there are certain guarantees that sending an item actually reached the other site, and which makes guaranteed resource handoff through channels a bit easier.

Re:Go hits the concurrency nail on the head by zbentley on Tuesday October 09, 2018 @11:22AM (#18176655)
> It operates on bytes and not on objects, so a custom protocol is needed on top of it.

That's why typed channels are useful, at least at the copying level (when it's more than just an array of lockable memory addresses underneath--data has to actually get transferred)--the typing is the message delimiter, which itself is the protocol.