Slashdot Mirror

← Back to Stories (view on slashdot.org)

Pthreads vs Win32 threads

Posted by ryuzaki0 on from the different-situations,-different-needs dept.

An anonymous reader writes "It's interesting when different people have different opinions. While I was searching for something on Intel's website, I came across an article on why Windows threads are better than Posix threads. Curiously, I also came across this article on why Posix Pthreads are better that Win32 threads. The thing is, both of these articles are written by the same author!

So who is right (metaphorically speaking?), or what has changed since the first article was written?"

3 of 385 comments (clear)

  1. Re:Look at the dates, Dude. by Anonymous Coward · · Score: 5, Informative

    Except that the 2006 entry is essentially a structural copy of the 2003 entry, just with some wording changes. He even uses the same arguments against PThreads in the second entry that he used to support it in the first. Weird...

  2. Re:PThreads is better by PhrostyMcByte · · Score: 5, Informative

    You're in luck-

    Vista comes with APIs for condition variables and reader-writer locks so you don't have to spend 15 minutes writing your own.

  3. Re:quothe the poster by PitaBred · · Score: 5, Informative
    Did you notice the other similarities?

    Initial (2003) article:

    I've used both POSIX threads (Pthreads) and Win32 threads APIs and I believe that Pthreads has the better programming model of the two. While each threading method can create threads, destroy threads, and coordinate interactions between threads, the reason I make this claim is the simplicity of use and elegance of design of Pthreads. Let me illustrate with a few examples.
    And in the later article:

    I've used both POSIX threads (Pthreads) and Windows threads APIs, and I believe that Windows has the better programming model of the two. While each threading method can create threads, destroy threads, and coordinate interactions between threads, the reason I make this claim is the simplicity of use and elegance of design of the Windows threads API. This is all from the perspective of multithreaded code developers or maintainers. Let me illustrate with a few examples.
    It's not plagiarism because he copied from himself and just added a few edits, but c'mon... how lazy of a shill can you be?
    --
    My blog. Good stuff (when I remember to update it). Read it.