Hacker News Reader

Comment by ketchupdebugger | Hacker News Reader

Its like forced conversion. It only benefits MSFT. Teams get to claim github as a customer, and MSFT saves some money. This might be small, but usually this opens the door to a whole suite of software being shoved down github's work/tech stack.

View on HN

I'm all for dogfooding, the only meaningful difference between slack and Teams to me, is the search for actual information that I know I've encountered in the past (it's easier on slack IMO), and the awesome way to interact/thread with conversations in a natural way.

Video-conferencing wise, I always have more problems with slack than with zoom/teams.

I mean... it's a pretty hard sell to say "Hey boss person, can we use our competitor's software to discuss company business?"

My team also used Slack when I joined and were eventually required to move to Teams. We aren't forbidden from using Slack, I'm in multiple Slacks collaborating with various OSS projects and foundations every day.

This way they also don't send all their internal company communications to a third party, which would be extra stupid when you have your own in-house conferencing software to use instead.

this already happened to some extent. the “blessed” way to develop github is in vscode (from ms), using codespaces (from ms), running on azure (from ms). vim/emacs users can use the terminal (although the codespace and port forwarding, at first, had to be done via vscode exclusively) but your entire toolstack needs to be installed each time you launch a new one.

collaborating with anyone at ms already meant you were using teams to some extent.

(former github developer)

Reply on news.ycombinator.com