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

231–240 of 344 posts

Re: The Horror of Microsoft Teams

#231

Post by gattilorenz »

broth wrote: post #195
mysterydip wrote: post #120

Earlier quoted context omitted.

Reminds me of the NET SEND command in windows 2000-xp. Allowed sending a popup text message to specific (or all with a wildcard!) machines on a network. Sure there were times where such a feature would be convenient ("server going down for maintenance, please save your work", etc), but overall ripe for abuse. They disabled it in a service pack and took it out altogether in subsequent versions.

Back in my senior year of high school during Spanish class I naively used NET SEND to send a message to one of my classmates. The only problem was that I failed to specify the user in the command and instead used *. This ended up sending a message to all computers in the school district. I remember the computer administrator coming into the class saying “Are you aware one of your students is sending messages to the e…

Same, apart from the suspension. On my first computer science class. That was... not fun.

The professor classified me as the annoying kid, until I surpassed his expectations with the first programming excercises :P

Re: The Horror of Microsoft Teams

#232

Post by aembleton »

andrewnc wrote: post #178
untog wrote: post #146

Earlier quoted context omitted.

You can make an efficient Electron app, just look at VS Code.

My VS code was using 10 GB of RAM today... It's better than other electron apps, but I would argue still not efficient

Did you open a 10GB file in it? Mine is using 200MB right now with a PHP project open in it.

Re: The Horror of Microsoft Teams

#233

Post by arethuza »

johnbatch wrote: post #112
stuart78 wrote: post #20

At my work, we use Teams a fair bit, and I'll go out on the limb to defend it (a limb I'm quite familiar with at this point ;) ). Thinking of it as a Slack alternative is, IMO, the wrong starting point. We barely use it for chat (as we have Slack as well). Instead, we use it as a file share and central information home. Each group within a team has a channel and we use the tabs to track meeting notes, embed external…

Doesn’t it just create SharePoint sites for each team on the backend and store the files in SharePoint? Even on 1:1 chat sharing a file just uploads it to OneDrive and uses OneDrive links.

Yes, each Team sits on top of an Office 365 Group so comes with all of the stuff that you get with an 0365 Group (SP Site, Planner etc.).

NB All Teams have 0365 Groups but not all 0365 Groups have a Team.

Re: The Horror of Microsoft Teams

#234

Post by richdougherty »

Apart from the notification noise drowning out important messages I'd like the ability to select messages and copy them. Sadly if you drag and select you only get the bit of the Electron DOM that's currently visible on the screen. Vote here: https://microsoftteams.uservoice.com/forums/555103-public/su...

Re: The Horror of Microsoft Teams

#235

Post by icebraining »

underwater wrote: post #220
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.…

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…

Microsoft had something called OLE just for that kind of embedding, and it was already cross-platform, as part of Office.

Re: The Horror of Microsoft Teams

#236

Post by evacchi »

Andrex wrote: post #111

Slack vs. Teams doesn't interest me as much as Teams vs. Hangouts Chat. Anyone here use both and can compare?

as a user of Hangouts Chat, reading this Teams description, they look terrible just the same. Misfeature-wise, they are very much alike.

Re: The Horror of Microsoft Teams

#237

Post by gadders »

mysterydip wrote: post #120
mullingitover wrote: post #7

> "This means that if someone does @${channel_name} you will get an alert. MS have not implemented muting as a feature. Secondly, for all those automatic/admin channels, you can’t unsubscribe yourself (or at least not with the default policies). Brilliant, isn’t it? Unavoidable alerts that any idiot on any channel can annoy people with." At my last job we figured out the fastest way to get your company off Teams: add…

Reminds me of the NET SEND command in windows 2000-xp. Allowed sending a popup text message to specific (or all with a wildcard!) machines on a network. Sure there were times where such a feature would be convenient ("server going down for maintenance, please save your work", etc), but overall ripe for abuse. They disabled it in a service pack and took it out altogether in subsequent versions.

Back in 2002 or so, NET SEND was a vector for spammers to send messages over the internet as well.

https://tweaks.com/windows/37362/stop-net-send-spammers/

Re: The Horror of Microsoft Teams

#238

Post by dillonmckay »

mopsi wrote: post #77
bluedino wrote: post #47

Microsoft ruins Skype, then tries making their own communication tool. Ugh. What is it again that Microsoft is getting such accolades for? Visual Studio Code is fantastic. Github is great, but they bought that. Office 365? OneDrive? I'll give you those. Hosted Exchange is a thorn in my side. Internet Explorer and Edge are (were?) both a joke. I don't have any experience with Azure. Xbox is great. Their server product…

In my experience, Windows 10 is a decent OS under the hood (eg, working with SMB network shares is much more robust compared to Mac), but the GUI completely ruins the experience. Win 10 is filled with annoyances like using no less than five different visual styles for right-click context menus. Not to mention Settings app that uses the same font and color for text and clickable links: there's no way to tell buttons a…

I was setting up Outlook on a new Windows 10 laptop, and copied the .pst files over.

When I opened Outlook to navigate to the open file dialog to add the .pst file, the bottom of the dialog asked what I want to save the file as...

Re: The Horror of Microsoft Teams

#239

Post by baud147258 »

underwater wrote: post #220
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.…

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…

Office 365 could just as easily be opened in the browser, instead of slowing down the app for all users. I mean it's a chat app, how many users are going to need to edit a document inside the app?

Re: The Horror of Microsoft Teams

#240

Post by benparsons »

Jaruzel wrote: post #208
opencl wrote: post #114

Earlier quoted context omitted.

There are already a bunch of native Teams/Slack/etc.-like applications. Matrix has a good number of native clients[1]. There's Ripcord[2] which supports both Slack and Discord. There's Matterhorn[3] for Mattermost. [1] https://matrix.org/clients/ [2] https://cancel.fm/ripcord/ [3] https://github.com/matterhorn-chat/matterhorn

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.
Post reply on HN