31–40 of 77 posts
Hi all, In addition to being the submitter, I'm also the author and a member of the Pony core team. I'll check the comments here from time to time and answer what I can.
The website does not show any code in the first or second page. Only a cheatsheet after 3 clicks - which is a pdf.
Earlier quoted context omitted.
Pony's model is different than Erlang's, so trying to think of it in terms of Erlang's model ("entering receive loop") may not be helpful when trying to understand it. The Pony runtime takes care of scheduling an actor to run when there is a message for that actor. The actor runs through the behavior and then waits to be scheduled again by the runtime when another message is available. If you want to filter messages…
I get it, it's like event driven programming with static event handlers per actor. Where you can't express a wait for a specific message directly in the body of the function. But you still have to do it somehow, which is what my question was about, how do people do it in Pony. Typically in event driven systems to do this either nested callbacks are used or higher order programming (futures/promises, etc).
> Pony's reference capabilities and Rust's borrow checker both provide data safety; they just approach it in different ways and have different tradeoffs. Would like to see a summary of what those tradeoffs are. Very curious!
This won't be an exhaustive answer, but I can asnwer a little. Also note, this is purely based on my own experiences with Rust (and Pony) and from what I've heard from other folks as well. Both are difficult for folks just learn the languages to grasp. When I tried doing async programming in Rust, I found the borrow checker especially hard to deal with. Pony's reference capabilities, once you understand them, apply q…
I'd like to do a comprehensive comparison someday, but just don't have the time...
Earlier quoted context omitted.
The website does not show any code in the first or second page. Only a cheatsheet after 3 clicks - which is a pdf.
You'd be looking for the tutorial: https://tutorial.ponylang.org/
You could consider some runnable demos like python and rust's. [1], [2]
Earlier quoted context omitted.
This won't be an exhaustive answer, but I can asnwer a little. Also note, this is purely based on my own experiences with Rust (and Pony) and from what I've heard from other folks as well. Both are difficult for folks just learn the languages to grasp. When I tried doing async programming in Rust, I found the borrow checker especially hard to deal with. Pony's reference capabilities, once you understand them, apply q…
Being the dual of Sean, I know Rust super well, but don't have as much experience with Pony, especially newer versions. This basically corresponds to my understanding as well. I also say "Pony is like Rust with Erlang" too. I'd like to do a comprehensive comparison someday, but just don't have the time...
Earlier quoted context omitted.
Hi spooneybarger. I'm curious: why is 1/0 == 0? Is it because there is no way to panic/kill the current actor with an error?
That's covered in the Pony tutorial. https://tutorial.ponylang.org/gotchas/divide-by-zero.html I can elaborate a bit on what is in the tutorial. With the current semantics, you as the application programmer can check for division by zero and throw `error` if you want. Otherwise, every division operation would be partial which given that pony forces you to handle all partial functions, can get to be very painful. We a…
Earlier quoted context omitted.
You'd be looking for the tutorial: https://tutorial.ponylang.org/
It would be good to show off the language more prominently, on the home page. You could consider some runnable demos like python and rust's. [1], [2] [1]: https://www.python.org/ [2]: https://www.rust-lang.org/en-US/
Also, pony is still an early product. It's secure, but it still needs more work before extremely important work happens using pony.
In that regard, it's better to attract only those who propel themselves then to attract a bunch of users who wont/cant contribute and will impose their demands on the core team.
It's just not time to market yet.
Earlier quoted context omitted.
Pony's model is different than Erlang's, so trying to think of it in terms of Erlang's model ("entering receive loop") may not be helpful when trying to understand it. The Pony runtime takes care of scheduling an actor to run when there is a message for that actor. The actor runs through the behavior and then waits to be scheduled again by the runtime when another message is available. If you want to filter messages…
So kind of like the RabbitMQ worker/message/job dynamic?