4 ms·

There's more context if you scroll down in the thread. In my opinion, they should try to support more browsers sooner and build on standards, but I do understan

There's more context if you scroll down in the thread. In my opinion, they should try to support more browsers sooner and build on standards, but I do understand starting with the browser that has the biggest market share to prove out the feature, then expanding from there. --- "We're afraid our first response may have come off a little more limiting that we meant it — we're focusing on Chrome for our calls support specifically, but that does not mean we have no plans to expand to other browsers in the future!" --- "Apologies — our initial tweet wasn't as clear as it could have been. We didn't mean to imply that future support for other browsers is off the cards, just that it's not on the cards right now."

dustinmoris 9y ago
> We didn't mean to imply that future support for other browsers is off the cards, just that it's not on the cards right now If something is not on the cards RIGHT NOW then it doesn't mean "we released this feature on Chrome first and the rest is following", it means "we don't believe in cross browser support (=diversity) unless enough people scream loud enough". A very web damaging attitude in my opinion.
- AndrewKemendo 9y ago
  "we don't believe in [foo] unless enough people scream loud enough" Every piece of advice about how to build products gives this exact advice. Why is it not applicable to Slack? Because of their funding amounts? Again, this is a genuine question, why is the case of slack different than any other company?