Hacker Timesnew | past | comments | ask | show | jobs | submit | jtfmumm's commentslogin

I'm the author of this post. I'm happy to answer questions.


I'm the author of this post and I'm happy to answer questions here.


Thank you for the informative blog post, this is the type of well-written detailed technical post with solid use case (rather than vague sales-ey ones) that pushes me to give a chance to new software.

I had never heard of Wallaroo before your post, but quite impressed. If this works, this can solve a lot of problems. I like the price tiering and great to see a NYC company amidst a sea of Valley ones.


Thanks! That's great to hear.


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.


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.


Very cool, thanks for sharing!


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.


> we thought mapped well onto the actor model.

Out of curiosity, were there a widely accepted actor lib/approach in Rust (I know there are a few like RobotS and others), would that have affected your decision?


It might have. When we were looking at Rust, it was a topic of conversation.


In general, it's not a space where there's a hyper-mature library, but there are some cool stuff happening today: http://cityboundsim.com/devblog/my-full-rustfest-talk-with-n...

That said, I mean, if you want to go full actors, Pony is a great choice.


Oh wow, I used to follow Citybound development a while ago when it was still written in JS. Anselm is an amazingly talented developer and it's great to see him working with Rust!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: