News for hackers. Stuff that matters.
Re:Go Python, Go: Stream Processing for Python by dajonker on Thursday October 12, 2017 @10:11AM (#15458024)
What about the use of Pony? I did not hear about it before but I do like some of the ideas of the language I read on their website. However, they also state "Pony is pre-1.0. We regularly have releases that involve breaking changes. This lack of stability is plenty of reason for many projects to avoid using Pony." How are you going to deal with that?
Re:Go Python, Go: Stream Processing for Python by spooneybarger on Thursday October 12, 2017 @10:29AM (#15458183)
I personally work at both Wallaroo Labs and am on the Pony core team. A number of engineers at Wallaroo Labs are committers to Pony. We are active members in the Pony community and a large driver of many of those breaking changes to Pony. At least 3/4 of the breaking changes to Pony over the last 9 months came from us at Wallaroo Labs. From our side it's not particularly problematic to make the occassional update.
Re:Go Python, Go: Stream Processing for Python by fermigier on Thursday October 12, 2017 @11:52AM (#15458854)
"At least 3/4 of the breaking changes to Pony over the last 9 months came from us at Wallaroo Labs." -> And you're proud of yourselves ?!?

(Just kidding of course).

Re:Go Python, Go: Stream Processing for Python by spooneybarger on Thursday October 12, 2017 @11:58AM (#15458909)
I'm going to be writing a blog post on this, but you inspired me to touch on it a bit.

When we went looking at what we should use to implement Wallaroo, one of the things that appealed to us about Pony was that it was a high-performance actor based runtime that we could help mold. We gave consideration to writing our own implementation in C but, we'd still be working on that rather than talking here on HN now if we had.

Pony has gotten us quite a bit. The runtime was used for a number of production projects at one of the major banks so we knew that while there might be some bugs (what code doesn't have them) that we could use it to jumpstart our process.

I gave a talk about Pony and its relation to Wallaroo where I put out the figure of 18 months. I think that as a wild ass guess, using the Pony runtime saved us about 18 months of work to build the foundation we want/need for Wallaroo.

Speaking as a member of the Wallaroo Labs team, it's really nice to have a community based project that you can help mold and grow with. It's been a boon to us as a small development shop in a way that either writing from scratch ourselves or using an existing more widely used runtime wouldn't be.

Speaking as a Pony core team member, I encourage other companies who think they could benefit from a high-performance actor based runtime to have a look at Pony. You could have a large hand in shaping it into the runtime that you need.

Re:Go Python, Go: Stream Processing for Python by devy on Thursday October 12, 2017 @10:48AM (#15458349)
There are quite a interesting ideas floating on Quora about Pony[1]. Unfortunately, after the demise of Casualty where the original authors worked, the language didn't seem to go anywhere.

[1]: https://www.quora.com/What-is-your-experience-with-using-Pon...

Re:Go Python, Go: Stream Processing for Python by spooneybarger on Thursday October 12, 2017 @11:00AM (#15458453)
Speaking as a member of the Pony community, the Pony community has done quite well since Casuality ceased to exist. I addressed this on the Pony mailing list a while back:

https://pony.groups.io/g/user/topic/on_the_state_of_pony/251...

I'd also like to note that the statement that Sylvan is no longer involved in the Pony community in that post is very offbase. He's a founding member of the Pony core team and still actively involved.

Re:Go Python, Go: Stream Processing for Python by 0cachecoherency on Thursday October 12, 2017 @11:22AM (#15458630)
Hi, I'm Sylvan Clebsch, the designer of Pony. I'm very much involved in Pony, as are most of the Causality founders in various ways. It's unfortunate that this kind of misinformation keeps being passed around.
Re:Go Python, Go: Stream Processing for Python by devy on Thursday October 12, 2017 @12:10PM (#15458984)
Good to know that Sylvan! Honest suggestion: you should debunk that misinformation on Quora which has a bigger audience than HN here.