I old but not too old, I was lucky(unlucky ?) enough to still had to write C++ mutli-threaded code in my first job.
No matter how good I thought (spoiler, I wasn't), many a bugs could have been traced back to my erm "understanding" about what is safe and proper threaded code.
If you have to do things in parallel or concurrent (lol calm down now HN, I know there is a difference). I'd say just go look at GO !
Damn once you get the hang of channels and CSP concept. It's so beautiful and elegant ! :) I'm sure there are many counterpoints and it doesn't fit every problem, but as a professional cs practitioner, you owe it to yourself to give Go and it's paradigms a fair and open mined go !
Oh and the built in race-detector is glorious tool ! The "feeling" you get when you got a zillion fibers/channels going and the race detector reports no issue is like "levelling up" !
Sorta how if you serious about CS/Coding you have to at least install a LISP once in your lifetime - even if you do nothing with it but swear and squint :) #duck !
No matter how good I thought (spoiler, I wasn't), many a bugs could have been traced back to my erm "understanding" about what is safe and proper threaded code.
If you have to do things in parallel or concurrent (lol calm down now HN, I know there is a difference). I'd say just go look at GO !
Damn once you get the hang of channels and CSP concept. It's so beautiful and elegant ! :) I'm sure there are many counterpoints and it doesn't fit every problem, but as a professional cs practitioner, you owe it to yourself to give Go and it's paradigms a fair and open mined go !
Oh and the built in race-detector is glorious tool ! The "feeling" you get when you got a zillion fibers/channels going and the race detector reports no issue is like "levelling up" !
Sorta how if you serious about CS/Coding you have to at least install a LISP once in your lifetime - even if you do nothing with it but swear and squint :) #duck !