Thanks for the follow up Eric. Your experience with the concurrency primitives lines up with my experience porting projects from various languages into Go. The ability to maintain exceptionally low cognitive overhead when adding concurrency is pretty amazing.
On an unrelated note, if in the future you find yourself converting more projects and need the advanced regexp features you can use this regexp implementation: https://github.com/dlclark/regexp2 It's closer to what you're used to with Python (or C#, or Javascript, etc), but those advanced features do have a cost that shouldn't be entered into lightly. - Doug On Friday, February 21, 2020 at 11:08:53 AM UTC-6, Eric Raymond wrote: > > This is a belated addition to my notes on the Go translation of > reposurgeon. I'll be adding it to the revised version I post to golang-dev. > > One extremely positive thing I must say before closing. Translation from > Python, which is a dreadful language to try to do concurrency in due to its > global interpreter lock, really brought home to me how unobtrusively > brilliant the Go implementation of Communicating Sequential Processes is. > The primitives are right and the integration with the rest of the language > is wonderfully seamless. The Go port of reposurgeon got some very large > speedups at an incremental-complexity cost that I found to be astonishingly > low. I am impressed both by the power of the CSP part of the design and > the extreme simplicity and non-fussiness of the interface it presents. I > hope it will become a model for how concurrency is managed in future > languages. > > > -- 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/0113e65f-c809-476b-a9b4-c0ab4830134f%40googlegroups.com.
