<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mixing Metaphors: Actors as Channels and Channels as Actors (Extended Version) · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1611.06276/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1611.06276/feed.xml" rel="self" type="application/rss+xml" /><item><title>Mixing Metaphors: Actors as Channels and Channels as Actors (Extended Version) — mentioned by Zalastax</title><link>https://news.ycombinator.com/item?id=17668233</link><guid isPermaLink="false">urn:hackerpapers:mention:1611.06276:17668233</guid><pubDate>Thu, 02 Aug 2018 00:13:17 GMT</pubDate><description>&lt;p&gt;I find this resource confusing and annoying to read. When performing my thesis research I wasted a bunch of time trying to make sense of Hewitt&amp;#x27;s writing. I think a big problem is that the term &amp;quot;actor model&amp;quot; is so overloaded that it almost becomes meaningless. The actors that Hewitt is talking about is not at all the same as Erlang or Akka. As an example I consider this quote from the text nonsensical &amp;quot;Actor systems can perform computations that are impossible by Turing Machines&amp;quot; or of very little relevance to the actor models we use for programming. This has been discussed at [0]. For an…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1611.06276/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
