Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I worked on a team (of nine) which tupled a lot.

Using Linux, I, and one other, was therefore not able to participate in a lot of work. Coworkers would pair with others because of familiarity, and because between macos and linux, there was more friction.

This caused a severe schisma in an already disfunctional team.

Management then disallowed tuple, because it was making things worse. But the practice continued. I quit. Not because of Tuple, but the entire distinction, of which Tuple was an ingredient.

The choice to not support an important part of the developer community is understandable from technical perspective. But socially, in times of isolation, home offices etc, it is doing harm out there.



Nobody is forced to use Tuple. If you blame anyone blame that company for allowing anyone to use Tuple in the first place, or the asshat engineers that held it against the Linux people.


Sure.

My point is that any company that makes a co-operation product, but which excludes a demography from co-operating, should know they are causing harm.

Imagine if slack excludes Android. Or Google Meet excludes Apple devices. That is not only a poor product, it causes minorities to be excluded. Or divides the companies or teams using it. This is what Tuple is doing.

I'm blaming both Tuple for not including Windows and Linux up-front, just as well as management adopting such tech that has these clear limitations.

In this practical case, the Linux (and Windows) users joined later into an "mac-only" team. Tuple, however, was the major cop-op tech: they refused Slack, accidentally used Telegram (!?) and email, and when using Google Meet all engineers refused to turn on webcams. So as a non-Tuple-using person you were really kept out of the loop.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: