[lbill]

It might be a bit early to accuse Walaroo of wasting money into "fun for coders" and ignoring the market's actual needs.

When I read their blog, I get the feeling that they are thinking things through. They seem to target a specific market and focus on what can make their product desirable. And yes, they are definitely experimenting on a few things but they are well aware of the trade off: it appears to be a calculated risks, and might very well pay off in the near future.

[EDIT]: typo

[swsieber]

Given what I know of Pony, WhatsApp and Erlang, it reminds me of WhatsApp's decision to write their backend in Erlang.

And it is a risk - big whoop, you've written production code in Pony. Good luck doing that again elsewhere, or hiring someone competent in it. I don't think it's quite hip or popular enough to be very useful on your resume (but I could be wrong).

[dna_polymerase]

> Good luck doing that again elsewhere

If keep doing stuff because its done elsewhere we stop innovating.

> it reminds me of WhatsApp's decision to write their backend in Erlang.

WhatsApp's decision to use erlang is based upon totally valid points. In fact Erlangs concurrency model made scaling so easy for them, they only needed 50 engineers overall for handling 50B messages a day. [0]

You might not know Pony, that doesn't mean it couldn't make sense for someone else.

[0]: http://highscalability.com/blog/2014/2/26/the-whatsapp-archi...