We have plenty to do dsacco. I agree. re: emphasizing Pony, the moderators here on HN changed the title of the post, adding Pony and also redirected it to GitH

We have plenty to do dsacco. I agree. re: emphasizing Pony, the moderators here on HN changed the title of the post, adding Pony and also redirected it to GitHub repo so, don't have a ton of control over that. The blog post that announces the release specifically talks about the Python API which is what we are initially supporting. re: C++. C++ was our first API but the folks we have gotten traction with aren't those that are interested in using C++. We have limited resources and a lot of work to do, so, the C++ is there and folks can use it if they want but we don't want to mislead people into thinking that it will get the same attention as the Python in terms of features or bug fixes in the near future. In the end with C++, we will pick it up and start working on it more if it can bring in revenue and allow us to grow the team and further enhance the product. At the moment, most of the interest that we are getting is for Python, Python 3, and Go so we are putting an emphasis there. We had to make the hard decision in August that C++ wasn't getting traction and we shouldn't be investing time in that API at this time. Handling multiple concurrent failures will be addressed by the end of the year as will logging. We've put a lot of work into some areas and less into others. You have nicely highlighted a couple that we de-emphasized initially. Thank you for your kind words and congratulations. edit to add a bit more info re: timing on a release. I think that is hard for any project. Whether it has commercial backing or not. In the end, we want to get Wallaroo out there with people, warts and all and get feedback from folks on what features they think are most important. We want to hear from potential users in the space and have them help us prioritize functionality (even more so if they pay us money so we can hire more engineers to speed development).