Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub staff are required to use Teams by Sep 1, 2023

twitter.com

Post reply on HN
Print view View original

101–110 of 725 posts

Re: GitHub staff are required to use Teams by Sep 1, 2023

#101

Post by cassianoleal »

ss108 wrote: post #95
nkotov wrote: post #40

Earlier quoted context omitted.

I had to use Teams for a couple of months with a client. It's not great but it's not terrible. I do miss days of Zoom but I opened it recently and found apps listed during the call of sudden - felt like bloatware.

Not sure what you missed about Zoom. It's works, but doesn't feel smooth and seems to have a very big footprint for something with a specific use-case. In particular, my day job is at a big corpo office space style place, and the software that requires the most updates is Zoom. I don't get why. It's also a lot less simple to use than Google Meet

One of my clients insist on using Zoom. I have never installed it (after so many security issues in the earlier days, I'd rather not risk it). I just use it from the browser.

Every time I click to open a meeting it downloads the installer, which IMO is a horrible dark pattern. I despise them as a company, and don't find their product anything special.

That said, using it on the browser has an effectively null footprint and doesn't require updates.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#102

Post by dmonitor »

samcat116 wrote: post #5

Teams isn’t great compared to Slack for async text chats, however the video conferencing is actually quite good and I didn’t have any real issues moving from Zoom to it.

I don't think Teams even has a sound test. It just places a call with a microsoft bot that repeats the audio back.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#103

Post by dgellow »

creshal wrote: post #92
rwalle wrote: post #37

What's the problem with "4 yr old laptops"? My colleagues and I use Teams on computers 1-5 years old and haven't heard about any issues.

"4 year old laptop" can mean anything from "8 cores, 64 GB RAM, dedicated GPU" to "720p display, 4GB RAM, dual-core". If Github for whatever reason punished its employees with the latter, well. Teams is not the world's most optimized Electron app.

720p, 4GB in 2019?

Re: GitHub staff are required to use Teams by Sep 1, 2023

#104

Post by dmonitor »

tootie wrote: post #13

Maybe I'm nuts, but I see almost zero appreciable difference between any of the most common chat or video conference platforms. They all have some little quirks or bonus features, but 99% of the time I'm only using the core features that they all do the same. Slack is absurdly expensive for what it does. Slack Pro is $12.50/person/mo. It's the same price for O365 which includes chat, video and the entire Office suite…

Discord must be kicking themselves for going after the gamer market instead of offering a professional platform. It beats pretty much every other video conferencing app I've used.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#105

Post by cyberge99 »

belter wrote: post #91
w0m wrote: post #50

Earlier quoted context omitted.

That's overtly harsh take I think. Teams has issues; but asking employees of a company to use said companies tools internally isn't necessarily a bad thing. Hard to improve without dogfooding.

Team has issues is the understatement of the year. A simple feature like screen freeze has been requested per use in the thread below hundreds of times... "Between different messaging boards (including the link above) this feature has been requested over 2000 times (1044 times as of this writing on the link above alone). Could Microsoft chime in to let us know if this is going to be on the roadmap? Thanks." https://a…

They don’t even have something as simple as a key combo to mute and other basic functionality (macos).

Re: GitHub staff are required to use Teams by Sep 1, 2023

#106

Post by number6 »

thomastjeffery wrote: post #67
w0m wrote: post #50

Earlier quoted context omitted.

That's overtly harsh take I think. Teams has issues; but asking employees of a company to use said companies tools internally isn't necessarily a bad thing. Hard to improve without dogfooding.

That's the problem: Microsoft isn't a company. They aren't a cohesive team working on a product. They are a corporation: a group of companies with separate trends writing on separate products. Is the GitHub team working on Teams now? I doubt it.

I hope they do. This can only improve Teams

Re: GitHub staff are required to use Teams by Sep 1, 2023

#107

Post by tootie »

bombcar wrote: post #73
yamtaddle wrote: post #35

Earlier quoted context omitted.

Nah, Zoom was wildly better than other options at first, but the rest these days are mostly OK enough to handle most day-to-day needs. And yeah, chat apps are pretty similar. ... except Teams, which manages to be possibly the single most confusing piece of software I've ever used. And I like Paradox games....

Zoom was amazingly batshit better than the competition (mainly gotomeeting) for actual conference calls because of how easy it was for someone who had never used it to start (which we later learned was because Zoom was pulling all sorts of clever bullshit to avoid installation dialogs). Once you're past the onboarding/installation hurdle, they all start to blend together.

WebEx used to own this market and is still going pretty strong. Ironically, WebEx has one really good feature that Zoom doesn't which is that you can actually zoom on a screenshare.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#108

Post by kimbernator »

jasonlotito wrote: post #89
kimbernator wrote: post #72

How is it possible that Teams is still such a poor product? I really didn't like it when my job switched like 6 years ago, and I don't recall ever feeling that it improved in any meaningful way. I switched jobs to one using Slack and it's not perfect but it is a lot better. It's almost a meme at this point. In the presence of other clients that have gotten it "right" (or at least more "right" than teams) like Slack,…

They are still using Slack. This is for video conferencing only. I've heard that with regards to video conferencing, it's competitive with zoom.

I've been in a "mixed" slack/teams environment and it seems there was always a push to be a little more teams-y every month or so - given that Github is owned by MSFT, I wouldn't be surprised if that happened there, too.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#109

Post by rickstanley »

belter wrote: post #91
w0m wrote: post #50

Earlier quoted context omitted.

That's overtly harsh take I think. Teams has issues; but asking employees of a company to use said companies tools internally isn't necessarily a bad thing. Hard to improve without dogfooding.

Team has issues is the understatement of the year. A simple feature like screen freeze has been requested per use in the thread below hundreds of times... "Between different messaging boards (including the link above) this feature has been requested over 2000 times (1044 times as of this writing on the link above alone). Could Microsoft chime in to let us know if this is going to be on the roadmap? Thanks." https://a…

Nice, I can't even view the first link because I'm redirected to a stupid MS login and I have blocked scripts, not even a message shows, just plain black screen.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#110

Post by thomastjeffery »

number6 wrote: post #106
thomastjeffery wrote: post #67

Earlier quoted context omitted.

That's the problem: Microsoft isn't a company. They aren't a cohesive team working on a product. They are a corporation: a group of companies with separate trends writing on separate products. Is the GitHub team working on Teams now? I doubt it.

I hope they do. This can only improve Teams

Why? What value does Teams bring to GitHub? They are totally separate techs.

I don't care at all about Teams. GitHub, on the other hand, is the host of many important projects. I would much rather the GitHub team be left alone to do their jobs.

Post reply on HN