Re:Channels are Actors
by noblethrasher on Friday August 03, 2018 @02:16PM
(#17682161)
It's worth noting that the submitter of the post is also the inventor of the Actor Model.
Re:Channels are Actors
by carlehewitt on Friday August 03, 2018 @02:21PM
(#17682224)
Fowler'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."
Do 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.
Re:Channels are Actors
by carlehewitt on Saturday August 04, 2018 @03:34PM
(#17688150)
Message passing communication is more fundamental than channel commutation.
However, lists {T*] of type T are very important; especially when they are used with Futures.
Re:Channels are Actors
by whalesalad on Friday August 03, 2018 @02:30PM
(#17682320)
"Actors that take put and get messages" – makes sense.
> What is the purpose of this post?
To advertise Code Mesh:
> To get the latest, see my upcoming Code Mesh Keynote:
Re:Channels are Actors
by carlehewitt on Saturday August 04, 2018 @10:39AM
(#17687005)
You can watch the keynotes for free after the conference :-)
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?