5 ms·
This article is wrong on so many levels... - It implies that async execution is equivalent to callback hell. In reality there are excellent ways to have async
by onestone 11y ago
This article is wrong on so many levels...
- It implies that async execution is equivalent to callback hell. In reality there are excellent ways to have async code which looks just like sync (generators, async/await).
- It benchmarks multi-core (sync) vs single-core (async) and makes claims based on the results.
- It presents async execution as an antipode of clustering. In reality it's a best practice to make use of both.
...and everything that follows is just irrelevant.
- weddpros 11y agoIn addition... "PUT commands write to a file, GET commands read the file back, sort and reduce the data, then return the file" I guess the author had to add the sort/reduce to "prove" his point...
- rajeevk 11y agoThere are so many statements in the article that makes me laugh > async cons: Adds latency with parallel overhead What parallel? This should be cons for multi threaded running on single core cpu > async pros: Callbacks help enforce error-prone synchronization How does callbacks help in error prone synchronization? It is not callback, it is single threaded model that does.