Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Threading: real pain or just whining?

Name: Anonymous 2008-06-07 15:17

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.

Name: Anonymous 2008-06-07 17:49

This book is written for VB developers
This book is written for VB developers
This book is written for VB developers
This book is written for VB developers
This book is written for VB developers
This book is written for VB developers
This book is written for VB developers
Thread over.

Name: Anonymous 2008-06-07 18:23

>>2
I believe Dan's cautionary tale applies to virtually all developers currently working in Windows. Programming with threads is hard because:

 • our current programming models don't deal with concurrency well
 • most of the programming we do is linear in nature
 • programmers have a hard time thinking in terms of events than can interrupt each other at any time
 • i'm a whining bitch.


Thread continues

Name: Anonymous 2008-06-07 18:32

codinghorror.com

Name: Anonymous 2008-06-07 18:33

joelonsoftware.com

Name: Anonymous 2008-06-07 18:41

prog.org

Name: Anonymous 2008-06-07 19:05

>

Name: Anonymous 2008-06-07 19:15

myothercar.com

Name: Anonymous 2008-06-07 20:30

myothercar.com.    86400    IN    CNAME    cdr.com.

Name: Anonymous 2008-06-07 21:36

Developers on Windows! Hah! No serious develop uses that platform.

Name: Anonymous 2008-06-07 21:39

BAWWWWWWWW I'M TOO STUPID TO KNOW HOW TO USE THREADS BECAUSE I'M A VB CODE-WRITER

sage for VB tripe.

Name: Anonymous 2008-06-07 22:03

VBCODE

Name: Anonymous 2008-06-07 23:00

Perhaps with a language that has better treatment of concurrency, DAN would not be such a whiny bitch.

Name: Anonymous 2008-06-07 23:31

My other CAR is a C.A.R. Hoare.

Name: Anonymous 2008-06-08 0:24

My other C.A.R. Hoare is a a whore

Name: Anonymous 2008-06-08 12:56

because of that link i ended up reading about xbox multicore issues from john carmack and then perusing the java.util.concurreny class docs by doug lea. thank you for reminding me that i suck at programming compared to those people

Name: Anonymous 2008-06-08 14:33

>>16
You suck at programming compared to /prog/, because you were interested in java/microsoft topics.

The game, you have just lost it

Name: Anonymous 2008-06-08 17:31

>>17
faggot

Name: Anonymous 2008-06-09 2:49

Threads are not the only way to implement concurrency

(don't tell it to Windows programmers).

Name: Anonymous 2008-06-09 5:28

I prefer to minimize thread use if possible. I am a big fan of using select()/poll() in enterprise servers

Name: Anonymous 2008-06-09 5:40

>>20 Told you -- do't tell it to Windows programmers.

Name: Anonymous 2008-06-09 8:31

>>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]

Name: Anonymous 2008-06-09 9:05

>>22
even the most inspired java code is going to be a fraction the performance of pedestrian native C
INCORRECT

Name: Anonymous 2008-06-09 13:39

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.

Name: Anonymous 2008-06-09 19:01

>>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

Name: Anonymous 2008-06-09 20:37

>>25
lol adequate.

Name: Anonymous 2008-06-09 22:58

>>22,24-25
You're all a bunch of faggots who are just repeating what you've read in some idiot's blog. As someone who's both written software in C for ARM7 and ARM9, and written software in Java for what's essentially a modified ARM9, I can tell you that you're incorrect.

I'm not sure how you think the JVM is implemented on embedded systems, but if you think that C is considerably faster you're a retard. Why, you ask? Why would an interpreted language run faster than a native binary?

Because the ARM architecture has an extension which allows it to run Java bytecode natively called Jazelle[1]. While I'd argue that for some benchmarks Jazelle is slightly less performant than the equivalent C code (because of how ARM extensions work), it isn't a difference you'll notice as a normal developer.

You faggots should stick to what you know -- instead of bitching about real-world performance issues (which you clearly have no experience dealing with), instead complain about Java's blatent lack of critical language features like closures.

________________________________________________
[1] http://www.arm.com/products/esd/jazelle_home.html

Name: Anonymous 2008-06-10 2:25

>>27
You're BBCode expertise has convinced me that you know what you're talking about.

Name: Anonymous 2008-06-10 3:21

>>27
Right, Java just lacks critical language features like good generics. C#/.NET's implementation of generics is superior.

But seriously, you're right. Java hasn't been slow as shit since the early 2000's, but there are still plenty of other reasons to hate Java. My dream is a corporate-sponsored language with C#/.NET's awesomeness with the JVM's portability.

Name: Anonymous 2008-06-10 4:51

>>29
1. Write a .NET runtime in Java
2. Make it free (NOT GPL)
3. ???
4. Profit!

Name: Anonymous 2008-06-10 7:21

>>28
You're
I raged like a true aryan whose garden has been trampled on by jews.

Name: Anonymous 2008-06-10 8:31

>>29
I agree. Java vendors should abandon the language like the sack of AIDS-infested fail it is, and concentrate on running LISP in the JVM

Name: Anonymous 2008-06-10 9:59

>>32
From what I understand about the JVM that's impossible.

Name: Anonymous 2008-06-10 10:06

>>33
Would you care to elaborate?

Name: Anonymous 2008-06-10 10:12

>>34
It's NP-Complete.

Name: Anonymous 2008-06-10 13:03

>>34
EXPERT PROGRAMMERS please comment but I believe continuations are a bitch to do in the JVM.

Name: Anonymous 2008-06-10 13:18

Christopher would use Haskell and Software Transactional Memory.1

1                        

Name: Anonymous 2010-12-26 22:38

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List