3 ms·
A channel can behave like an actor but they are not the same thing. An actor is a living entity. A channel is a transit mechanism. What is the purpose of this
by whalesalad 8y ago
A channel can behave like an actor but they are not the same thing. An actor is a living entity. A channel is a transit mechanism.
What is the purpose of this post? To argue the academic definition of channels and actors? To spark a discussion on their uses and benefits?
- noblethrasher 8y agoIt's worth noting that the submitter of the post is also the inventor of the Actor Model.
- carlehewitt 8y agoFowler's talk addressed issues arising from "mixing metaphors" by having both channels and Actors in our programming languages. The point of this post is to point out that channels are best understood as Actors that take put and get messages thereby achieving a unification in our programming languages and conceptual framework. Of course, a channel can be conceived as a "living entity" and an Actor can be used as a "transit mechanism."
- whalesalad 8y ago"Actors that take put and get messages" – makes sense.
- jchassoul 8y agoDo you want to abolish the protagonist role of the channel abstraction like in CSP based languages and certain message brokers? We can't have issues with channels if we're all actors and don't impedance mismatch the mixture when building our systems.
- carlehewitt 8y agoMessage passing communication is more fundamental than channel commutation. However, lists {T*] of type T are very important; especially when they are used with Futures.
- zokier 8y ago> What is the purpose of this post? To advertise Code Mesh: > To get the latest, see my upcoming Code Mesh Keynote:
- carlehewitt 8y agoYou can watch the keynotes for free after the conference :-)