2018-09-21 01:20:07.225115+02 by Dan Lyke 3 comments
Why does everyone's thread abstraction library always make things more complex and harder to deal with than just using the pthreads API directly? (Today's facepalms brought to you by Apple)
[ related topics: Language Apple Computer Books ]
comments in ascending chronological order (reverse):
#Comment Re: Why does everyone's thread abstraction made: 2018-09-22 12:57:07.764064+02 by: DaveP
We’ve settled on Intel's TBB as our threads foundation. I’m most definitely not the expert, but it’s been less troublesome than most of the alternatives, from what I’ve heard.
#Comment Re: Why does everyone's thread abstraction made: 2018-09-23 20:23:08.588745+02 by: TheSHAD0W
Because there are all these niggling little ways to get inter-thread communications and isolation wrong, so of course people make libraries that provide methods that do it properly. That have their own niggling little ways to get wrong.
#Comment Re: Why does everyone's thread abstraction made: 2018-09-24 02:52:45.35984+02 by: Dan Lyke
Yeah, I guess it's kinda like the people who think that C is too error prone, so they code in PHP... and don't sanitize their database inputs.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.