Thank you. Great interview. As expected, everything he said was true - especially when you read the full segment - one in about 50 presented. No wonder the original poster did not want to link to the full article. I’ll reiterate - “CS god”.
I did a quick review of k8s - and it is almost equal usage of sync.Mutex and channels throughout the code. So in practicality - Go “do not share data” mantra is not easy to achieve in practice. Go channels are simply two versions of a queue - a handoff or a buffered blocking queue. Java has many others. Similarly, as Brian points out - Go has non-reentrant sync.Mutex. Java has multiple synchronization primitives to support a wider variety of use cases. I encourage everyone to read the article - it’s an excellent interview (even if you disagree on the small reference made to Gos concurrency model). > On Oct 2, 2022, at 6:21 AM, 'Dan Kortschak' via golang-nuts > <golang-nuts@googlegroups.com> wrote: > > On Sun, 2022-10-02 at 06:15 -0500, Robert Engels wrote: >> Again, I would like a link to the source of statement to evaluate it >> in context. > > https://manningbooks.medium.com/interview-with-brian-goetz-7d6c47d05d63 > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/3d6ff1822f402e745cdc51776fcf6bfd0a112d75.camel%40kortschak.io. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1911A3CC-0C01-494F-94BA-CF00FE98AE1F%40ix.netcom.com.
