3 ms·
I would say this article is a far cry from "nonsense" - it's quite informative, even if there are a few small inaccuracies or naming issues.
by daveidol 4y ago
I would say this article is a far cry from "nonsense" - it's quite informative, even if there are a few small inaccuracies or naming issues.
- xxs 4y agoThere quite a few inaccuracies. The fact they are ok w/ using a naked sleep and w/o checking the interrupt flag is a flag on its own. (if you want sleep w/o exceptions use LockSupport.parkNanos not lombok) The more glaring one is the fact that stack memory uses virtual memory space and it's not 'allocate' until used. On 64bit OS it means it's quite cheap. To me that's an unmissable, if one has spent any time doing anything with io or threads in any capacity. There is a distinct different between parallel tasks and concurrent ones and the article seems to be confused about that part as well. (There is a reason the term is 'embarrassingly parallel' instead of 'embarrassingly concurrent')