Pthreads vs Win32 threads
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?"
So who is right (metaphorically speaking?), or what has changed since the first article was written?"
( Pthreads >= Win32 threads ) and ( Win32 threads >= Pthreads ) => Pthreads = Win32 threads
If you are programming on Widows I would recommend Windows threads, while on *nix Pthreads are a better choice.
One uses lowercase and underscores. The other uses studlycaps and Hungarian notation. It is an aesthetic choice.
So one might say that intel goes both ways?
I'm used to reading comments on slashdot, but this one confuses me -- what is smoneys?
Get it right, assmuch. It's Linsucks or Linsux.
Vista is the coolest OS ever. OS X 10.4 is a total rip off of it.
> Who gives a shit. They're just threads, man. Both work.
You know, I said this very same thing back in the 70s. However, my buddy with the bell bottoms and KISS shirt got more play than I ever did with my adidas shorts and Vader cape.
I hope, when they die, cartoon characters have to answer for their sins.
I have different theory: Dude has 2 separate threads in his brain. Comparing pthreads to Win32 threads only exposed dangerous race condition producing funny effects in his blog.
839*929
"It's interesting when different people have different opinions."
No it is not.
Q)Why did the multithreaded chicken cross the road?
A)to To other side. get the
Q)Why did the multithreaded chicken cross the road?
A)other to side. To the get
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
Everytime I see a win32 API I have to weep. I'm really wondering what drugs their engineers are on, and they can't be good ones.
What are you talking about? Plenty of people code for Windows, we call them "virus writers". ;)
>Get it right, assmuch. It's Linsucks or Linsux.
It's GNU/Linsux you bastards! When are you going to get it right! Arghh!
Open Source Drum Kit, LPLC deve board - mjhdesigns.com
We have always been at war with Pthreads. We have never been at war with Windows threads.
The submitter is clearly nuts. Everyone knows that we have always been at war with Windows threads. Anyone who suggests we're at war with Pthreads is insane.
--<Mike>--
You're saying you typoed "semaphores" as "mutexes"? Wow, that's a hell of a finger-slip. Anyway, fuck you. Oops, sorry about that typo, I meant "take care."
Q) Which came first, the multithreaded chicken or the multithreaded egg?
A) They came at the same time, but the multithreaded chicken terminated first.
Q) Which came first, the multithreaded chicken or the multithreaded egg?
A) Neither; mt egg could not acquire chicken-lock from mt chicken. mt chicken could not acquire egg-lock from mt egg.
Q) Which came first, the multithreaded chicken or the multithreaded egg?
A) Multithreaded egg, but it overwrote its DNA while still in use and became mt turkey.