GopherCon 2017: Kavya Joshi - Understanding Channels

just the best

If we are multiplexing g1 and g2 on one os thread arent we at the mercy of the scheduler , for e.g. we can just execute g1 enqueue forever if the channel is not full and no work is done

Ofc this is assuming one os thread, does go have enough context not to use the same thread?


@google

awesome

Thanks for the amazing informative content Gopher Academy. The speaker explained everything in very detailed crisp and with nice presentation.

Fantastic talk

Way cool explanation. The best teacher. W'd luv to see more explanations from here.

Loved this!

Kavya has become a synonym for Channel

great; expect more talks

The style is a bit too cheesy but the contents is very interesting.

It is helpful to me extremely

Does anyone know where can I get the slides？

Brilliant talk. Learnt a lot.

Great explanation of channel mechanics!

Seriously, the question is still "why channel?" versus the simple use of a mutex? They're both blocking. If channels block everywhere, obviously using a mutex is clearly better. All channels do is to move the isolation from one place (which can be a bottleneck) to another (a smaller bottleneck). All the "cool" things mentioned aren't cool, just necessary things not to block everywhere. What would be cool is what makes channel a communication means preferred over mutex.

Cool thanks 👏

Rob Pike and Kavya Joshi do best go talks. Change my mind.

great talk!

awesome and simple talk!

Why does she sound so aggressive?

where is the pre？

gdd

Great talk!

in case of early reader, G1 decides to write directly to G2 memory location, how does it resume the G2? also how does it tell G2 not to read from buffer? the pending instruction in G2 is to read from buffer right?

this is a great talk thanks but I don't like calling things "magic", actually we amaze me about go it is reasonably easy to understand what will the code does

Many thanks!

This is such an amazing talk, makes clear inner working of channel. This will help to write concurrent codes more better way than I am doing today in go

Ok. That go routine modifies stack of the other, for performance to do the trick.
.
.
.
.
.
.
.
.
(searches how to learn rust faster)

there is a 1 element lifo as well for performance benefits

Great talk!

Great Talk!! Thank you for such an insight into Go Channels

Great talk

Great talk. Learned lots of useful things. Great formatting. I could see all the details of the slides on my 13" screen

this is the best talk ever on concurrency and channels, Thanks Gopher Academy and Kavya Joshi

Great talk! One of the best!

I have just started playing with channel. Thanks for this talk 👍

great presentation!

Very well done. Thanks for this amazing contribution.

really amazing talk !

Thanks, so clear

She explained the implementation of channel in such a understandable way, great talk!

Kavya Joshi -done it in an understanding manner...presentation slides was also superb..

Wish she had written a book..Or is there such a book about internals of Go concurrency primitives.

Really awesome talk

Great talk, thank you so much

Excellent , i know the channel a lot that i ever have

Excellent material and presentation, thanks you.