Re:Why events are a bad idea for high-concurrency servers (2...
by axismundi on Thursday January 30, 2020 @11:15AM
(#22192478)
and then there was that just two days ago: https://news.ycombinator.com/item?id=22165193
[ Parent
| on HN ]
Re:Why events are a bad idea for high-concurrency servers (2...
by TheFiend7 on Thursday January 30, 2020 @11:22AM
(#22192535)
Haha I think that's the point of OP's post IMO, and people were even discussing this dichotomy in that thread as well.
Total gold, nothing in this world is clean or definitive.
Re:Why events are a bad idea for high-concurrency servers (2...
by gpderetta on Thursday January 30, 2020 @11:44AM
(#22192770)
Yes :). I do not actually have a strong opinion on the Event/Threads/Coroutines debate. I think they should all be considered on a case by case basis.
Re:Why events are a bad idea for high-concurrency servers (2...
by bullen on Thursday January 30, 2020 @07:50PM
(#22197803)
I'll restate the same thing I commented on that post:
https://news.ycombinator.com/item?id=22174201
People only now start to understand that the problem with multi-core is memory speed and the only way to solve that is by using a virtual machine with a concurrent capable memory model = Java.
In-lined memory does not play well with multiple threads. Cache-misses is the way to parallelize code!