4 ms·

For a bit of context on what is Pony: http://www.ponylang.org http://www.ponylang.org . Are there any users of the language that would care to comment on using

For a bit of context on what is Pony: http://www.ponylang.org http://www.ponylang.org . Are there any users of the language that would care to comment on using the language?

spooneybarger 10y ago
In addition to being a member of the core team, I work at a company that uses Pony and working with it every day has been a pleasure. There are plenty of rough edges to work out but the compiler has stopped me from introducing subtle data-races into our code base on more than one occasion (more like at least once a week, if not more).
- thepumpkin1979 10y ago
  What company is that, what business is it in?
  - spooneybarger 10y ago
    Sendence. We are a start up in the high speed data analytics space. We have an emphasis on going as fast as possible while remaining accurate.
doublec 10y ago
I've used it in a few personal projects. I've written some thing about it here: https://bluishcoder.co.nz/tags/pony/ https://bluishcoder.co.nz/tags/pony/ The two major things that I stumbled on when I first started using Pony was that there is no blocking constructs in the language and dealing with capabilities. I've had exposure to memory safe languages using types before (ATS, Rust) so the Pony system of capabilities wasn't too difficult to understand once I was able to map them to things I was familiar with. Before that I struggled to understand why things weren't compiling. Now that things have somewhat clicked I'm pretty productive with the language. Dealing with writing non-blocking code was a matter of thinking in terms of callbacks and promises - something familiar to a lot of Node programmers I suspect. Once I got past those two things I find the language very nice to write in and easy to reason about the code. Sometimes I hit walls of struggling to work out why things aren't compiling and they eventually end up being the compiler showing me what I was trying to do would be unsafe due to data races, etc. The language is still young though so definitely something to approach with a bit of understanding that things may break.
- 35bge57dtjku 10y ago
  Interesting website.
karma_vaccum123 10y ago
We know the value of constraining reference capabilities from Rust (`mut` annotations etc). Now imagine you could annotate these references even further, describing how they specifically operate wrt concurrency. To me, that is where Pony shines. We'll see more of this in other languages.

For a bit of context on what is Pony: http://www.ponylang.org http://www.ponylang.org . Are there any users of the language that would care to comment on using the language?

spooneybarger 10y ago

In addition to being a member of the core team, I work at a company that uses Pony and working with it every day has been a pleasure. There are plenty of rough edges to work out but the compiler has stopped me from introducing subtle data-races into our code base on more than one occasion (more like at least once a week, if not more).

thepumpkin1979 10y ago
What company is that, what business is it in?
- spooneybarger 10y ago
  Sendence. We are a start up in the high speed data analytics space. We have an emphasis on going as fast as possible while remaining accurate.

doublec 10y ago

I've used it in a few personal projects. I've written some thing about it here: https://bluishcoder.co.nz/tags/pony/ https://bluishcoder.co.nz/tags/pony/ The two major things that I stumbled on when I first started using Pony was that there is no blocking constructs in the language and dealing with capabilities. I've had exposure to memory safe languages using types before (ATS, Rust) so the Pony system of capabilities wasn't too difficult to understand once I was able to map them to things I was familiar with. Before that I struggled to understand why things weren't compiling. Now that things have somewhat clicked I'm pretty productive with the language. Dealing with writing non-blocking code was a matter of thinking in terms of callbacks and promises - something familiar to a lot of Node programmers I suspect. Once I got past those two things I find the language very nice to write in and easy to reason about the code. Sometimes I hit walls of struggling to work out why things aren't compiling and they eventually end up being the compiler showing me what I was trying to do would be unsafe due to data races, etc. The language is still young though so definitely something to approach with a bit of understanding that things may break.

35bge57dtjku 10y ago
Interesting website.

karma_vaccum123 10y ago

We know the value of constraining reference capabilities from Rust (`mut` annotations etc). Now imagine you could annotate these references even further, describing how they specifically operate wrt concurrency. To me, that is where Pony shines. We'll see more of this in other languages.