QCon NY: Pony
Post with link to my 2017 QCon New York talk “Pony: How I learned to stop worrying and embrace an unproven technology” and associated content.
Polyconf'17: Why Pony?
Post with link my Polyconf’17 talk “Why Pony? Bleeding edge technology for your concurrency woes”.
Pony Patterns: Waiting
I am a patient boy. I wait, I wait, I wait, I wait. My time is water down a drain Everybody’s moving. Everybody’s moving. Everything is moving, moving, moving, moving Please don’t leave me to remain. In the waiting room — Ian MacKaye How do you wait when you can’t wait? No, that isn’t a riddle; it’s a question I recently faced while writing some Pony code for work.…
Inside the Pony TCP Stack
In this post, we are going to take a look at how Pony implements its TCP stack. The API for Pony’s networking stack is callback and event driven. I’ve previously written about network programming in Pony and showed how to implement a simple echo server. We didn’t, however, dive too deeply into the Pony TCP stack. In this post, we’ll move down a level of abstraction and see how Pony implements classes that handle TCP socket programming in an actor friendly, event-driven fashion.…
Deconstructing a Pony echo server
Lately I’ve been diving into learning Pony in a more organized fashion. As part of that, I’ve decided to share the experience along the way. If you aren’t familiar with Pony then you probably won’t get much from this post. If you are interested in a high performance, safe, actor based programming language, then I’d suggest you check out the Pony tutorial then venture back. All that said, I’ll do my best to provide links to relevant Pony documentation throughout this post.…