Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

But then you get into a whole heap of problems with multiple threads.


sort by: page size:

And nowadays you can throw in multithreading problems into the mix.

It's all fun and games until you start dealing with C++ thread issues.

Which is why you break the task into multiple threads.

Threads are evil at the application level - IMHO.

> writing applications which are multi-threaded

Well that's your problem right there.


Everybody solves that by having multiple threads (either at the OS or runtime level), so you can run in parallel the stuff that don't conflict with each other.

You can have 2) with the additional complexity / upside of multiple threads

Right but that's the developer's fault for not understanding how to do multithreading correctly.

Except that multi-threaded applications are inherently more complex and are extremely challenging to debug.

Multithread is not as easy as you think for a legacy application this big.

I agree strongly with this. Multithreaded code is super hard to understand and super error-prone when you're dealing with threads and locks yourself.

The problem with this is you only get 1 thread for the UI and other stuff to run on.

Depending on your problem you can actually lose performance with a multi-threaded app due to the context switching overhead.

Multi threading brings in all kinds of security issues

Multi-threading is easy it's synchronization that's hard.

Multi-threading is only hard if you share state. Keep state separate and life is good.

You can implement that on top of threads.

That depends on if developers can be convinced to actually use multiple threads...

Yep. Multithreaded coding is hard.
next

Legal | privacy