News for hackers. Stuff that matters.

jtfmumm

I'm the author of this post. I'm happy to answer questions.
Re:Stateful Multi-Stream Processing in Python with Wallaroo on Thursday December 07, 2017 @10:11AM (#15870636)
Thanks! That's great to hear.
Re:Stateful Multi-Stream Processing in Python with Wallaroo on Thursday December 07, 2017 @08:01AM (#15869609)
I'm the author of this post and I'm happy to answer questions here.
Re:Why we used Pony to write Wallaroo on Friday October 27, 2017 @04:20AM (#15566584)
We decided for a number of reasons that the JVM wasn't the right fit for us, so we didn't end up considering Kotlin.

Pony is being actively developed, and has been as long as we've been using it. Since some of our team are now core contributors to the language, we've also invested in improving Pony, which has proven to be very useful to us.

Re:Why we used Pony to write Wallaroo on Thursday October 26, 2017 @01:00PM (#15560777)
Interestingly enough, none of us had even written anything significant in Pony when we made the initial tentative decision. After we came to the conclusion that it might be a good fit, we started a test project and a couple of us tried ramping up as fast as we could. It was actually only after we decided it was the right choice that we started to get actively involved in the community.
Re:Why we used Pony to write Wallaroo on Thursday October 26, 2017 @12:47PM (#15560612)
I'm an engineer at Wallaroo Labs and I've been writing Pony for the last two years. We're using pony_stable (which is the primary package manager at the moment) and make for managing builds. I currently use Sublime 3 as my editor and lldb for debugging. I know that others are using emacs and vim as well.

We did consider Rust as there are certainly overlaps in their approaches to safety (though coming from different angles). In the end we thought that Pony would be better for managing concurrency for our particular use cases, which we thought mapped well onto the actor model.