Can we collectively stay calm and within the bounds of polite discourse? The overall tone of this thread is pretty aggressive.
I would also like to point out that this particular topic of discussion - the credentials of the author of the original article - seem fallacious to me from either side. They can neither be used to elevate arguments - that'd be an appeal to authority - nor can they be used to dismiss them - that'd be an ad-hominem. The original article and the related design documents contain more than enough material to have a reasoned, substantive discussion, without litigating the character and credentials of their authors. I find them all pretty well-written and reasoned TBQH. --- As far as that quote goes: I haven't read the full interview, but I tend to agree with the substance of that quote, personally. I myself have noticed that I rarely use channels and "real" CSP. I've also noticed especially novices to the language "overusing" channels, creating hard to understand and often buggy code. I think with discipline and adhering to a couple of rules can make them safe and lead to easy to understand code - but I find it often easier to "just slap a mutex on it", if you will. I don't think it can be argued that Go's concurrency model is particularly safe on its own. Especially not with a language like Rust existing and gaining mainstream attention. I think that's fine and I still think goroutines and channels are a net benefit (it does make it significantly easier to add concurrency). think Go's overall simplicity still makes it easier to write understandable, mostly bug-free software, than many other languages I've tried. I don't think any of this is an attack on the design of Go. I obviously love the language, despite these concerns. I just don't advertise its concurrency features as much to novices as I used to. On Sun, Oct 2, 2022 at 3:13 PM Jan Mercl <0xj...@gmail.com> wrote: > On Sun, Oct 2, 2022 at 3:04 PM Robert Engels <reng...@ix.netcom.com> > wrote: > > > One other thing, if you don’t think he knows exactly how Go routines are > implemented you are delusional. > > Maybe he should then fix the Wikipedia article I linked before. Good > luck with that. > > PS: I assume you meant "goroutines" instead of "Go routines". > > -- > 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/CAA40n-WXjyeW6uHkWvXJyRKxdSmvgbRObkS_%2BxTENSOCRW770A%40mail.gmail.com > . > -- 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/CAEkBMfE-eExBacz2c1OXtzAPU9NUsNzBBa135yiJFubgvE9bJA%40mail.gmail.com.
