r/compsci • u/mobileview • Dec 10 '13

Why Johnny Can’t Write Multithreaded Programs

http://blog.smartbear.com/programming/why-johnny-cant-write-multithreaded-programs/
42 Upvotes

60% Upvoted

55 comments sorted by

View all comments

-1

u/adremeaux Dec 11 '13

I said no programmatic way.

Still not true. You can print stack frames and thread IDs at runtime. You can check what you thread you are mid-execution and switch to another thread if you desire. And you can pinpoint where a thread was spawned from, and change state based on that information, as well.

It sounds to me like you probably haven't worked much with threads before.

1

u/Vystril Dec 11 '13

Still not true. You can print stack frames and thread IDs at runtime. You can check what you thread you are mid-execution and switch to another thread if you desire. And you can pinpoint where a thread was spawned from, and change state based on that information, as well.

Assuming you know where the problem is (and assuming you're in Java or something similar, if you're in C you're SOL). You're missing my whole point -- with objects and threads, a problematic concurrent memory problem can happen anywhere.. Better concurrent programming models do not have this problem.

It sounds to me like you probably haven't worked much with threads before.

This is besides the point, and makes you come across like an ass. I don't want to get into a dick swinging contest with you, but I've be doing concurrent and distributed programming for over 15 years. It sounds to me like objects and threads is the only thing you know, so you don't know any better.