<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>jodal.dev - actors</title>
    <subtitle>Personal blog of Stein Magnus Jodal</subtitle>
    <link rel="self" type="application/atom+xml" href="https://jodal.dev/tags/actors/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://jodal.dev"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2019-05-07T00:00:00+00:00</updated>
    <id>https://jodal.dev/tags/actors/atom.xml</id>
    <entry xml:lang="en">
        <title>Pykka 2.0 released with better ergonomics and performance improvements</title>
        <published>2019-05-07T00:00:00+00:00</published>
        <updated>2019-05-07T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2019/05/07/pykka-2.0/"/>
        <id>https://jodal.dev/2019/05/07/pykka-2.0/</id>
        
        <summary type="html">&lt;p&gt;I’ve finally released &lt;a rel=&quot;external&quot; href=&quot;https://pykka.readthedocs.io/&quot;&gt;Pykka&lt;/a&gt; 2.0, the
first major update to Pykka in almost six years.&lt;/p&gt;
&lt;p&gt;Pykka is a Python implementation of the actor model. The actor model
introduces some simple rules to control the sharing of state and cooperation
between execution units, which makes it easier to build concurrent
applications.&lt;/p&gt;
&lt;p&gt;Pykka 2.0 is a major release because it is backwards incompatible in several
minor ways. However, the backwards incompatible changes should only affect
quite narrow use cases.
Mopidy and its extensions,
which is the largest open source ecosystem I know of that uses Pykka,
runs unmodified on Pykka 2.0.&lt;/p&gt;
&lt;p&gt;In this blog post I’ll go through some of the more important improvements in
2.0.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Pykka, and porting Pykka to Python 3</title>
        <published>2011-03-29T00:00:00+00:00</published>
        <updated>2011-03-29T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2011/03/29/pykka-and-porting-pykka-to-python-3/"/>
        <id>https://jodal.dev/2011/03/29/pykka-and-porting-pykka-to-python-3/</id>
        
        <summary type="html">&lt;p&gt;This is somewhat of an introduction to &lt;a rel=&quot;external&quot; href=&quot;https://pykka.readthedocs.io/&quot;&gt;Pykka&lt;/a&gt;,
a Python library implementing the actor model, which I’ve been working on now
and then since November. And it’s still just 300 lines of code!&lt;/p&gt;
&lt;p&gt;The goal of the actor model is to make it easier to develop concurrent programs
by removing all shared state and use messaging for all communication. Removing
shared state and doing lots of messaging doesn’t make anything easier by
itself, but it avoids common problems in concurrent programs like proper lock
usage and data corruption (due to the absence of proper lock usage). Also, I
believe the actor model makes it easier to reason about concurrent programs,
which is a nice property since software development often feels like 10%
development and 91% debugging.&lt;/p&gt;</summary>
        
    </entry>
</feed>
