3 ms·
I don't know what can we learn from analyzing a poorly written program aside from what not to do. If the program was properly written there wouldn't be any iss
by DeathArrow 2y ago
I don't know what can we learn from analyzing a poorly written program aside from what not to do.
If the program was properly written there wouldn't be any issues with multithreading.
The title of the article gives the false impression that multithreading is slowing programs in the general case. In fact poorly written programs are slow and that is true for both multithreaded and singlethreaded programs.
If your program runs slow but you don't need it to run fast, don't bother.
If your program runs slow and you need it to run fast, go see what optimizations can be done.
- nlitened 2y ago> the false impression that multithreading is slowing programs in the general case. In fact poorly written programs are slow From my experience, in the general case programs are poorly written, so yeah, multithreading makes them 1) more complex, more poorly written, and 2) slower in many cases.