News for hackers. Stuff that matters.

n3otec

Re:Pony – High Performance Actor Programming on Monday May 04, 2015 @09:27AM (#9485964)
Thank you! :-)
Re:Pony – High Performance Actor Programming on Monday May 04, 2015 @09:19AM (#9485931)
Yes we are working on this. In the meantime, https://github.com/CausalityLtd/ponyc/tree/master/examples might be a good start!
Re:Pony – High Performance Actor Programming on Monday May 04, 2015 @09:06AM (#9485864)
No. If actor X is waiting for actor Y and Y for X and neither of the two has messages to process, they are potentially subject to GC.

The question is, what does X is waiting for Y mean? 'Waiting' would imply that there are language constructs to actually wait. Pony doesn't have that. An actor that is blocked (i.e. has no messages) and that satisfies necessary RC invariants will be collected.

Re:Pony – High Performance Actor Programming on Monday May 04, 2015 @09:01AM (#9485835)
Insallations instructions will be available today.
Re:Pony – High Performance Actor Programming on Monday May 04, 2015 @08:59AM (#9485824)
No. Dynamic linking is possible, for example with C libraries. 'No loadable code' means that a programs code is not modified during runtime, nor extended with new code (for example like java applets or RMI applications). We have been looking into hot code loading though.
Re:Pony – High Performance Actor Programming on Sunday May 03, 2015 @08:12PM (#9483637)
not yet, but it will be soon, and with the same causality guarantee
Re:Pony – High Performance Actor Programming on Sunday May 03, 2015 @07:20PM (#9483486)
In Erlang, that only holds for a pair of processes, as you point out.

In Pony, it holds for the entire program. So, if A1 sends a message to A2, and then A1 sends a message to A3, and in response to the second message A3 sends a message to A2... in Pony, A2 is guaranteed to get the message from A1 before the message from A3.

Re:Pony – High Performance Actor Programming on Sunday May 03, 2015 @06:51PM (#9483397)
We have been working on distribution support. We should get it into the runtime soon!