Ready to learn Pony? Awesome.

Getting help

If you run into trouble while you are learning Pony, don’t worry, we’ve got you covered. If you are looking for an answer “right now”, we suggest you give our Zulip community a try. Whatever your question is, it isn’t dumb, and we won’t get annoyed. We only request that you follow proper etiquette:

  • Be polite and respectful. Constructive criticism is good, but it’s even more important that users get along and foster a welcoming community. Being rude won’t get your questions answered.
  • Be clear whether you are asking if something already exists in Pony (eg. “does Pony have X?”), or if you are requesting new functionality. We’ve received several messages asking about libraries or features present in other languages, by new users who weren’t familiarized with Pony’s philosophy or programming style well enough. Make sure that you understand what is your problem and if it makes sense in Pony’s ecosystem, and clarify your intention of proposing a change. Baseless suggestions will be ignored.
  • Don’t rush experienced users for immediate answers. This is an all-volunteer project, and folks will help whenever they are available. Also, Zulip makes it easy to keep conversations of the same topic in one place, so you can check later to see if someone has answered your questions.

The beginner help stream is a good starting point for basic questions. If you need more information on what is considered appropriate or inappropriate behaviour, check out our Code of Conduct.

Many folks encounter the same issues or have the same questions, be sure to give the frequently asked questions section of this website a read.

Think you’ve found a bug? It’s quite possible. Pony is a relatively young language that is still changing at a rapid pace and bugs do happen. Your best bet. Write to the mailing list with your issue and verify that you are experiencing an issue. Once a more knowledge member of the community confirms you are experiencing a bug, open an issue.

The Pony community while small is very helpful and inviting. We think you’ll find interacting with us to be an enjoyable experience. You can find a lot more community-related resources in the community section of this site.

Installing Pony

Ready to dive into Pony? Excellent! Please checkout the installation instructions for the ponyc compiler.

Getting started

We have a couple resources designed to help you learn, we suggest starting with the tutorial and from there, moving on to the Pony Patterns book. Additionally, standard library documentation is available online. The cheat sheet is meant to serve as a quick reference for the main ideas that you’ll encounter as you begin to learn Pony.

Reference capabilities

If you are like most people learning Pony, your biggest stumbling block is going to be reference capabilities. Reference capabilities look like a very foreign concept to most folks. This isn’t surprising as they are one of the ideas that make Pony unique. Lots of folks get frustrated while learning reference capabilities and end up thinking that Pony has “too much type system” or is “too hard”. While we don’t agree with such assessments, we will agree that they can be quite hard for some folks to get a handle on.

What are reference capabilities

Reference capabilities allow you the programmer to use the Pony type system to guarantee that you are safely handling data in your application. If you try to do something unsafe, your program won’t compile.

What background do I need?

We’ve noticed that folks who have the easiest time with reference capabilities tend to have a couple things in common:

  • Familiarity with at least one strongly-typed language
  • Experience working in a highly concurrent, non-actor based language

If you are coming from a dynamically typed background then reference capabilities are probably going to be doubly hard for you. Why? Well, you are going to be learning to navigate general type errors in general and then, you’ll have the added overhead of reference capabilities related type errors. It’s quite possible to get over the hump but just be aware you are in for a bit more work. More important than your type system background is your “concurrency background”.

While reference capabilities might seem exotic, they aren’t really. They codify in the type system safe data handling practices that many programmers have learned over the course of time. If you have previously worked in a highly-concurrent, thread-based programming language like Java or C++ then there’s a chance that you have a leg up on learning reference capabilities.

We’re not going to pretend that all programmers know how to safely handle data when using threads. If they did, we wouldn’t need Pony. The sad fact is, handling data correctly when you have many threads is hard. Even the most experienced programmer makes mistakes and they are really hard to go back and find. That said, if you are at least used to thinking about how different threads interact with data in your program, you have a leg up. Reference capabilities are all about describing for the compiler how data should be handled.

So, if you are coming from a single-threaded language like Ruby or Python, odds are, you haven’t thought a lot about many threads safely accessing your variables. That’s ok, it just means you are going to have more work to do on understanding the concepts that the various reference capabilities represent. If you get hung up on something, don’t worry. We’re here to help.

Reference capabilities resources

A note about code samples

All recommended resources are incredibly helpful but represent Pony at a given point in time. While the core concepts will remain static, it’s possible that individual code examples will no longer compile with the latest versions of Pony. Pony is pre-1.0 and breaking changes are still quite common. If you run into code that doesn’t work, reach out and get help.

There are 4 primary resources that we currently recommend for understanding reference capabilities:

We suggest you start with John Mumm’s excellent overview “Safely Sharing Data: Reference Capabilities in Pony” and Chris Double’s “Reference Capabilities, Consume and Recover in Pony”. They are both good general overviews of reference capabilities and why they exist. From there, continue on and watch Sylvan’s Pony Virtual Users’ Group presentation on “Writing Generic Code”. A lot of what you see and watch in that video is going to go over your head. Don’t worry, that happens to everyone. We suggest that you pair it with “Bang, Hat and Arrow in Pony”. It’s an excellent write-up of the concepts introduced in the video. If you are looking for a slightly more academic take, Adrian Colyer did an excellent write up of Deny Capabilities for Safe, Fast Actors. It’s an overview of Pony’s reference capabilities.

Generics and references capabilities are the hardest things to get a handle on while learning Pony so don’t get frustrated. It’s not just you. We all go through this. During the video, you’ll hear one of our core team members, Sean T. Allen, commenting at numerous points that he was sort of following everything but not all of it. Sean now has a strong grasp on all the concepts. It takes time.

Our recommendation is to watch the video, read “Bang, Hat and Arrow in Pony” and then try writing code that uses generic classes like collections. Once you have a handle on using generic classes, move on to trying to write your own generic classes. All the while, repeatedly return to watching the video and reading the accompanying blog post.

Don’t worry. You will get it. And remember, the helpful Pony community is waiting to assist.