News for hackers. Stuff that matters.
Re:Goroutines: The concurrency model we wanted all along by quadcore on Friday July 07, 2023 @06:15PM (#36638993)
It does become a channel mess. The trick I use is to code everything using the same patterns (down to the same characters, name conventions, line breaks, etc) as much as I can so i can use the text editor to work (refactor) that mass. It's definitely the less funny part and why I'll still use clojure and it's async.io module whenever it makes sense (lots of different data). That way, I macro myself out of that problem.

Now if you cant use another language, change project. Go is not perl nor python, it's a sophisticated C. Use a sophisticated C for the wrong project / product and you'll want to kill yourself.

Re:Goroutines: The concurrency model we wanted all along by anacrolix on Saturday July 08, 2023 @09:39AM (#36644289)
It's more like a toothless C. In that it knows a bunch of tricks already, you can't teach it anything new, it can't bite you, and it's mostly harmless.
Re:Goroutines: The concurrency model we wanted all along by quadcore on Sunday July 09, 2023 @12:16PM (#36655762)
Thumb up to that.