4 ms·

They're not all lies per se. Tropo/Voxeo also isn't failing :/, they just won Deutsche Telekom's Euro business. Voxeo doesn't always have the best marketing te

They're not all lies per se. Tropo/Voxeo also isn't failing :/, they just won Deutsche Telekom's Euro business. Voxeo doesn't always have the best marketing team, but they do have a lot of technical expertise. Their CTO Jose is one of the funniest people I've ever seen on a panel and he's a delight to converse with. I don't think any of the metaphors at play here hit the nail on the head. Voxeo is a large, lumbering enterprise fighting its way into the Carrier world by virtue of erosion. Twilio is the nimble web-focused startup burning the candle at both ends trying to fight the night away. It's not yet clear which strategy will prevail, but I don't think the mudslinging is the right course either. Disclaimer: I'm the community manager at 2600hz, which is innovating on the application switching layer of voice communications. We're also full open-source.

robbiet480 14y ago
I say "Tropo is failing" and I mean that their adoption rate is much lower then Twilio is. I'm sure Voxeo has tons of money to throw at Tropo until they run out. I haven't heard of 2600hz before, great name. I'll check it out!
- josh2600 14y ago
  Thanks! We're total phreaks over here :D. Here's the Git link for our Kazoo project: https://github.com/2600hz/kazoo https://github.com/2600hz/kazoo Here's one of our APIs (conferencing): https://2600hz.atlassian.net/wiki/display/docs/Conferences+API https://2600hz.atlassian.net/wiki/display/docs/Conferences+A... We've got a client doing a very large number of simultaneous participants in a conference using this stack (in excess of 10k concurrent), so there's a lot of firepower here. Also of interest to this community: the logic is written in Erlang :). Let me know if you have any questions, we're in freenode at #2600hz
- mpermar 14y ago
  I am curious here. Is there any place to check Twilio or Tropo adoption rate? I'd love to get some numbers.
  - josh2600 14y ago
    Twilio has like ~150,000 devs in ~4 years, Tropo has like ~300,000 devs in ~16 years. Those are the numbers I hear thrown out, but I'd love to get some harder details.

robbiet480 14y ago

I say "Tropo is failing" and I mean that their adoption rate is much lower then Twilio is. I'm sure Voxeo has tons of money to throw at Tropo until they run out. I haven't heard of 2600hz before, great name. I'll check it out!

josh2600 14y ago
Thanks! We're total phreaks over here :D. Here's the Git link for our Kazoo project: https://github.com/2600hz/kazoo https://github.com/2600hz/kazoo Here's one of our APIs (conferencing): https://2600hz.atlassian.net/wiki/display/docs/Conferences+API https://2600hz.atlassian.net/wiki/display/docs/Conferences+A... We've got a client doing a very large number of simultaneous participants in a conference using this stack (in excess of 10k concurrent), so there's a lot of firepower here. Also of interest to this community: the logic is written in Erlang :). Let me know if you have any questions, we're in freenode at #2600hz
mpermar 14y ago
I am curious here. Is there any place to check Twilio or Tropo adoption rate? I'd love to get some numbers.
- josh2600 14y ago
  Twilio has like ~150,000 devs in ~4 years, Tropo has like ~300,000 devs in ~16 years. Those are the numbers I hear thrown out, but I'd love to get some harder details.