Screenhero changed my life for the better as a remote worker, and I was so sad when Slack acquired SH and blundered the acquisition i.e. just iceboxed the competition. (I learned Slack had their own architecture and codebase -- which is why it was worse -- so I'm inferring Slack acquired SH just to eliminate competitors, rather than use their code.) Tuple has been good so far, though I'm still noticing lag issues that are worse that Screenhero being. Even when connecting within the same city via strong internet, we can get pings of 200ms. It's unclear whether that's because of our internet or Tuple's infrastructure, we're still doing some testing.

Overall I've been pleased with Tuple. I think they're doing good work, care deeply about making a good product, and are looking into exciting features like mobbing support and supporting video. It's expensive, but so it goes when you want a good product.

If an alternative came up I'd at least try it out.

So far Tuple is answering my needs well. It is early in its life so I expect it just to get better, especially since its focus is on Pair Programming, and not all the other things that Slack is trying to solve.

BTW, thank you for setting the Gold Standard in pairing tools. I remember my Screenhero days very fondly and was sad to see what happened when Slack took over.