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

Ask HN: Why is Microsoft Teams still so bad?

news.ycombinator.com

Post reply on HN
Print view View original

201–210 of 814 posts

Re: Ask HN: Why is Microsoft Teams still so bad?

#201

Post by n8cpdx »

TurkishPoptart wrote: post #83
n8cpdx wrote: post #69

At least it doesn’t totally change the UI and hide all important elements when you start a screen share (Zoom). My experience has been pretty positive overall, at least for calling. Channels don’t work as well as slack, but it’s decent. The big trick is to run it in a browser so you avoid any electron overhead. It is fully featured in browser.

Can you tell me what you mean by electron overhead? Does that mean, like, the CPU resources it exhausts in the browser as opposed to the app is capped or reduced? Thanks

It’s a whole separate instance of chromium running to support the one app vs one instance of your browser running all of your websites and apps. I run Outlook, Slack (multiple instances), Teams, and Todoist as tabs in my browser rather than apps, and the experience is much better than using the native apps.

Re: Ask HN: Why is Microsoft Teams still so bad?

#202

Post by virgulino »

Maarten88 wrote: post #85

Long ago Microsoft had MSN Messenger, which was one of the leading messaging apps. It worked well, and many 'normal' users were using it. Then Microsoft dissolved the team behind it and screwed up the product so bad with bloatware and ads that everyone moved to WhatsApp (except in the US where people went back to texting). Then Microsoft came out with Communicator, renamed it to Lync, which was a corporate messenger/…

Not to forget that 26 years ago, starting in 1996, we had Microsoft NetMeeting.

https://en.wikipedia.org/wiki/Microsoft_NetMeeting

A very good VOIP / videoconferencing / white-boarding / application sharing client present on almost all Windows computers, open standards interoperable, with an official ActiveX Control and public API. You could easily embed it into your HTML site (IE compatible only), or drag and drop it into your Visual Basic / Delphi / Microsoft Office script application and thus effortlessly embed and control the functionality into your own website/application.

https://youtu.be/B8wH5pRcWts

https://news.microsoft.com/1996/09/30/microsoft-ships-netmee...

Re: Ask HN: Why is Microsoft Teams still so bad?

#204

Post by MikeTheGreat »

rchaud wrote: post #139
delecti wrote: post #102

Earlier quoted context omitted.

I think "military–industrial complex" is the typical term.

It is, but despite it being coined by a former US President and WW2 Allied General, it is now taken to mean something akin to "defund the military".

Could you clarify? I'm having trouble understanding the equivalency because "Military industry complex" is a noun and "defund the military" is a verb (more-or-less)

Re: Ask HN: Why is Microsoft Teams still so bad?

#206

Post by kevin_b_er »

Maarten88 wrote: post #85

Long ago Microsoft had MSN Messenger, which was one of the leading messaging apps. It worked well, and many 'normal' users were using it. Then Microsoft dissolved the team behind it and screwed up the product so bad with bloatware and ads that everyone moved to WhatsApp (except in the US where people went back to texting). Then Microsoft came out with Communicator, renamed it to Lync, which was a corporate messenger/…

"Skype for Business" was just a rebranded Lync. Consumer-land skype remained a different thing until Microsoft killed that for Teams. Skype for Business' exe was lync.exe right up until the end. "Teams" was a brand new thing and didn't use the Communicator/Lync/Skype for Business architecture.

Re: Ask HN: Why is Microsoft Teams still so bad?

#208

Post by vadym909 »

twobitshifter wrote: post #98
Maarten88 wrote: post #85

Long ago Microsoft had MSN Messenger, which was one of the leading messaging apps. It worked well, and many 'normal' users were using it. Then Microsoft dissolved the team behind it and screwed up the product so bad with bloatware and ads that everyone moved to WhatsApp (except in the US where people went back to texting). Then Microsoft came out with Communicator, renamed it to Lync, which was a corporate messenger/…

I started a new job and decided to go all in on using o365, including keeping notes in onenote. They’re launching a new version next month and I’m hoping that things go in the right direction and they keep the features i’ve just started to use.

The innocence is so cute in this one

Re: Ask HN: Why is Microsoft Teams still so bad?

#210

Post by coredog64 »

mBVth4DiupvBPY4 wrote: post #145
drewcoo wrote: post #133

Earlier quoted context omitted.

Microsoft had several different non-interoperable message apps, including two named "Messenger." Those golden days didn't look so shiny when we were there. Luckily, there was Pidgin/Adium, so we could have one app to talk all the protocols.

I'm not sure what you're referring to with two non-interoperable message apps named Messenger? There was MSN Messenger/.NET Messenger/Windows Messenger/Windows Live Messenger, but those were interoperable (they were the same thing, just updates). They also managed to wrangle compatibility with Yahoo Messenger (although by then no one I knew still used Yahoo), and apparently Facebook Messenger, and then did a crappy m…

NT had a built in messenger service that operated on named pipes. It was one of those services you disabled as soon as you could.
Post reply on HN