2 ms·
Well writing "hogging all the resources and chewing up cycles" shows he doesn't really get it at all. Not to mention that there's many reasons things can become
by MichaelGG 13y ago
Well writing "hogging all the resources and chewing up cycles" shows he doesn't really get it at all. Not to mention that there's many reasons things can become non-responsive without using the CPU. Like a shitty driver blocking on some timeout.
Sigh, "tech journalism".