4 ms·
The actor model deals with concurrent computation. The threading models on node and browsers do not allow concurrent computation, except for the case of web wo
by partycoder 9y ago
The actor model deals with concurrent computation.
The threading models on node and browsers do not allow concurrent computation, except for the case of web workers, and the proposed threading additions of JavaScriptCore.
Because of this, the actor model can be overkill when you have no threads. More specifically, you may introduce queuing where no queuing (or other type of synchronization) is necessary. This is because an actor is basically a worker with a work queue (aka mailbox).
For the most part promises can solve most of your async issues.
Event emitting/message passing is valuable, but queuing is optional in many cases.
- roperzh 9y agoHey, article author here, thank you for passing by! This is correct but misses the point of the article. The idea is to introduce the Actor Model to people unfamiliar with it, using one of the most popular languages out there.
- partycoder 9y agoHey, Scala/Akka user with many years of experience here, thanks for replying! The article is correct but misses the point of the actor model. The idea was to point out that the Actor model is about concurrent computation.
- boobsbr 9y agoPlease increase the contrast of the main text, it's uncomfortable to read. edit: I was reading it on Chrome on Android, it the main text looked gray and had poor contrast. Now I'm on FF 52 on Windows and the text looks black. Weird.