Threading: real pain or just whining?

http://www.codinghorror.com/blog/archives/000169.html

Aside from the VB.net faggotry, and the date of the post (2004 lol), i don't understand why is this people so scared of threads. Right, they add complexity, and a different way of considering problems, but sounds like they are trying to use them in the wrong place (like, everywhere). IMO, proper isolation and adequate locking for thread communication is enough, and doesn't really add any potential flaws to the code.

>>17
he doesnt completely suck at programming, since he read a john carmack post and john carmack said, and I quote:
[quote]The biggest problem is that Java is really slow. On a pure cpu / memory / display / communications level, most modern cell phones should be considerably better gaming platforms than a Game Boy Advanced. With Java, on most phones you are left with about the CPU power of an original 4.77 mhz IBM PC, and lousy control over everything.

 

I spent a fair amount of time looking at java byte code disassembly while optimizing my little rendering engine. This is interesting fun like any other optimization problem, but it alternates with a bleak knowledge that even the most inspired java code is going to be a fraction the performance of pedestrian native C code.[/quote]

With Java, on most phones you are left with about the CPU power of an original 4.77 mhz IBM PC, and lousy control over everything.
Fucking true. Many phones nowadays (even the cheap ones) are built around an ARM7/9 core and can hardly display a dozen of polygons per frame because of this fucking bloated shit. And it's not even portable.
In a perfect world, we would have a common C API (for thing like sound, 3D, input, video, network...) for ARM phones and we would be able to run ARM binaries directly on the phones, but that's not going to happen anytime soon.

>>24
Java's performance is adequate, assuming that the VM is not a complete POS, and you're not doing something extremely retarded. ARM7 should be enough for anyone