5 ms·
We should remember to distinguish between concurrent, parallel, and asynchronous programming. UI is a bad example for the reactor pattern, since the reactor pa
by klodolph 11y ago
We should remember to distinguish between concurrent, parallel, and asynchronous programming. UI is a bad example for the reactor pattern, since the reactor pattern is for concurrent processing and UIs should usually process events sequentially (but asynchronously). That's just a bog-standard event loop, not the reactor pattern.
"Practicing" different concurrency patterns sounds like a lot of tedious effort, and the suggestion to "go back to Node" seems a bit high-handed to me. I would encourage everyone to pick and choose what expertise they want to develop.
- frozenport 11y agoActually UIs process data synchronously, that's why - Qt for example doesn't need to std::mutex everything.
- klodolph 11y agoWhen I say "asynchrounous" I'm talking about the arrival of events. It's not a particularly well-defined word, though.
- deleted 11y ago[deleted]