On Sat, 2017-07-29 at 18:59 -0400, Shawn Milochik wrote: > […] > > Imagine if Go programmers went to other language mailing lists and > complained about the lack of goroutines and channels, which clearly > make > those other language "unfit for concurrent programming." That would > be > equally unhelpful.
Some of us have been going round various programming language mailing lists complaining about the lack of dataflow, CSP, etc. support in languages and their libraries for 30+ years. Fortunately, over the last 10 years, we have been getting programming language and libraries doing actors, dataflow, and CSP (or rough equivalent) properly, and most importantly – getting traction amongst programmers. So now we have a number of programming language becoming fit for concurrent and parallel programming, what is the next evolution? What comes after Go, Rust, Pony, Nim, D, C++20, etc.? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder -- 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. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part
