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

The Horror of Microsoft Teams

medium.com

Post reply on HN
Print view View original

281–290 of 344 posts

Re: The Horror of Microsoft Teams

#281

Post by cannonedhamster »

youdontknowtho wrote: post #269
realusername wrote: post #254

Earlier quoted context omitted.

Apart from some abstract legal paperwork requirements like those, I honestly don't see much difference between both privacy wise. If the company really requires privacy and owning their data, they should setup some hosted slack clone themselves.

It's not that a company owns their data, or needs privacy, its that they need tools to discover customer or even non-customer data from across the entire suite of systems that they use. It's a tremendous amount of data and MS built tooling that helps do that across all of their services. Setting up some kind of hosted solution in a country to comply with data sovereignty laws might be a solution, but it becomes a dat…

You can literally pull every single conversation private or not from Slack with a button push or email request. The company owns all that data. There doesn't appear to be anything special about how Teams does data retention from my perspective.

Re: The Horror of Microsoft Teams

#282

Post by dan-robertson »

Aaargh20318 wrote: post #257
underwater wrote: post #220

Earlier quoted context omitted.

It makes sense for Teams. The app is a chat client, sure, but it also contains the entirety of Office 365 and a third-party app platform. Chats can have tabs with Excel documents, wikis, polls, etc. By leveraging browser technology they have a platform that is incredibly extensible. Building that from scratch across iOS, Android, Windows and macOS is not feasible. And the benefit of having people reach to the tools a…

> Building that from scratch across iOS, Android, Windows and macOS is not feasible. Building a few chat apps is not feasible for one of the largest software companies in the world ?

This misses the point. The parent isn’t talking about just building a few chat apps. They are talking about building a chat app which can have basically any ms office thing embedded inside it.

Re: The Horror of Microsoft Teams

#283

Post by cannonedhamster »

ailideex wrote: post #252
moksly wrote: post #196

Earlier quoted context omitted.

I think Teams is exactly excellent because it allows you to secure your collaboration tool. Especially valuable post GDPR where you really don’t want your non-tech savy employers putting privacy data into some online Trello board, or slack/discord for that matter. The fact that teams is just part of your 365 platform is soooo awesome in non-tech enterprise that it’s hard to describe just how useful it is. But basical…

Why is it okay to put data in teams and not in trello?

Especially since Trello is owned by Atlassian. This one such me as weird too.

Re: The Horror of Microsoft Teams

#284

Post by zaphoyd »

acdha wrote: post #131
zaphoyd wrote: post #129

Earlier quoted context omitted.

RIP HipChat, last top tier native work chat program. We were paying customers for HipChat and were forced off when Atlassian killed it. Replaced by stride/slack/discord/teams all built on electron and all with awful non-native UI and web app like performance. I know why they do it: electron is cheap and easy to spam on every platform. I don't know why: people pay for this crap. Perhaps the issue is that people don't…

I’m curious what was so great about it: when we did the comparison even the Atlassian maintainers picked Slack.

It was a focused product. Native apps, high performance, no funny business. Yes, it lacked some features that the newer stuff had, but it did the team chat part really well and got out of your way.

Deploying web apps lets you iterate faster, stuff features in faster without ending up with different capabilities across the group of apps. Sometimes the ability to add features too easily is abused to add too many features without thinking through them.

Re: The Horror of Microsoft Teams

#285

Post by ck425 »

evilotto wrote: post #103

At my org, you'd never know that slack has muting as an option. @here in a nontrivial channel gets you public humiliation, every possible "loud" reaction thrown at you (to the point of hitting the slack limit on reactions) and people publicly scolding you that you just notified 500 people in 12 different time zones.

We used to have that, then there was a backlash and we're now far more tolerant. I'm not sure what the right balance is between not disturbing people and calling out folk (new joiners in particular) in from of the whole company.

Re: The Horror of Microsoft Teams

#286

Post by Jaruzel »

benparsons wrote: post #240
Jaruzel wrote: post #208

Earlier quoted context omitted.

What I want, is something that ISN'T a poor copy of Slack. We've lost the rich landscape of differing chat/collaboration clients, and now just have a mono-culture of Slack-Clones.

That isn't true at all - Matrix has a rich and growing ecosystem of chat clients. For Slack clones, you're well stocked, but the links given to you by the parent shows there is much more out there.

> Matrix has a rich and growing ecosystem of chat clients.

Including ones that work on iOS and Android WITH Notifications? Not having that feature has been a blocker for me so far.

Re: The Horror of Microsoft Teams

#287

Post by calvinv »

dleslie wrote: post #154
naikrovek wrote: post #152

Earlier quoted context omitted.

Who cares if an application's UI elements look the same across platforms? I want it to work on the platform I am using. I simply do not care what it looks like on someone else's platform, and I especially do not want to pay a performance penalty so some designer can have a virtual feather in their cap over it.

I prefer native widgets to whatever application-enforced fad of the year is current. Apps are lauded for providing "dark mode" now; when ten years ago I simply switched GTK themes. To say nothing of accessibility. We've gone way backwards in UX.

have you tried using OneNote in dark mode, it actually feels dark, like you can't see anything

Re: The Horror of Microsoft Teams

#288

Post by the_angry_angel »

acollins1331 wrote: post #81

Is there a reason that companies don't just use discord?

Off the top of my head;

* No Active Directory/SAML/other SSO. * Gaudy/gamer orientated look-and-feel, messages and notifications is hard to sell to business. * No/Poor implementations of "Enterprise Features" (read: eDiscovery, DLP, etc.)

Of those the first and second are arguably the most important as it is often a requirement for businesses of any size. The third is a bit more larger/enterprise-y business.

Re: The Horror of Microsoft Teams

#289

Post by Aaargh20318 »

dan-robertson wrote: post #282
Aaargh20318 wrote: post #257

Earlier quoted context omitted.

> Building that from scratch across iOS, Android, Windows and macOS is not feasible. Building a few chat apps is not feasible for one of the largest software companies in the world ?

This misses the point. The parent isn’t talking about just building a few chat apps. They are talking about building a chat app which can have basically any ms office thing embedded inside it.

Not real office, web-based office. Why not make a native chat app that opens Office files in the real full-featured Office ?

Re: The Horror of Microsoft Teams

#290

Post by hateful »

Solar19 wrote: post #139

The Teams client is built on Electron? Why? Developers need to stop building slow applications. This is ridiculous. It's 2019 and software is slower than it was in the 90s. It must take an enormous number of CPU cycles to execute simple tasks in an Election-based app. It's just incredibly inefficient. I heard similar things about Slack – that it was built on Node, maybe Electron, and was dog slow, especially to open.…

I know this doesn't speak to your comment, and is also a bit of a rant, but I would clarify that "tabs" in this respect are not like "tabs" in your browser, where you can have multiple "things" open at the same time. As soon as you leave the teams tab, that application/file is closed.

So if you have an excel file open in teams (which can take up at least 10 seconds - which does speak to your comment!), and want to go back to a channel or chat, you're actually closing that file.

Granted you can open the Excel file not in teams, but this is just an example of how being locked in one window where the tabs aren't your open items, but rather possibly open items, is counter-productive.

That brings me to something else that I find strange, that with every new piece of Windows software over the last 10 years, it seems like Microsoft forgot that it's called "Windows" for a reason. The big deal about Windows was having multiple WINDOWS. And every time you take that away, you stray further from productivity. Don't even get me started on multi-monitor support over the years! /rant

Post reply on HN