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

781–790 of 814 posts

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

#781

Post by another2another »

sumedh wrote: post #687
bko wrote: post #619

Earlier quoted context omitted.

This is a bad answer. It's actually a non-answer. You can apply this to a lot of questions. Why does X ... Y (because X can get away with it). There are real resources behind Microsoft Teams and a lot of people want it to be good. They may not get much of a signal about how well their product is doing compared to competitors because lock-in effects, but I can guarantee you the product managers and executives at Micro…

> but I can guarantee you the product managers and executives at Microsoft want the product to work well. MS cannot even work out there messenger strategy properly. We have/had MSN messenger, Skype, Skype for business, Lync and now Teams. What makes you think the execs in MS really care about messaging?

That they have so many products ? :)

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

#782

Post by deadlocked »

roydivision wrote: post #379

My 2 cents of venting on this sorry excuse of software - Backtick formatting in a chat post only works after typing the closing backtick, deleting it, re-typing it - Text copied from a conversation is polluted with names and time stamps. "I really want this feature" said nobody ever - The mute/unmute button is hard to find, I don't think I've ever attended a Teams meeting without someone struggling with this. Teams s…

I don't think I saw anyone mention it but you can't copy PNGs from a web page and paste them into Teams.

If I want to share graphs from LibreNMS with my team, I have to use the screenshot tool.

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

#783

Post by jrib »

vinhant wrote: post #134
jrib wrote: post #45

My company is transitioning to Teams and I find it frustrating. So much so that I collect my complaints in a confluence page. I could be wrong on some of these, so happy to be corrected! No links You can’t link to conversations. This means if you want to add context to a Jira ticket or in a code comment, you can’t easily do so. Inconsistent UI The UI between a Teams channel and a chat with multiple people is not cons…

Regarding code block, try ``` (backtick 3 times then space)

Thanks, adding the in chats does work!

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

#785

Post by auggierose »

jerojero wrote: post #759
auggierose wrote: post #324

Earlier quoted context omitted.

What is a horizontal community? Why you cannot build one with Discord? Which tool do you use instead for this task then?

I tried to set up a community with left-leaning people (politics). So we didn't really want the owner - admin - moderator structure that discord offered, instead we wanted a more open way for the community to self manage. The biggest problem came from the fact that we had been all in a discord server in the past that was deleted by the owner after a political disagreement. So in order for that to not happen again we…

Democracy. You're talking about a digital democracy!

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

#786

Post by happytoexplain »

winrid wrote: post #279
happytoexplain wrote: post #115

Still? It started good and became bad, like most software. And, as is also the norm, there is no amount of money that can fix shitty software unless you Ship-of-Theseus it, which is fundamentally at odds with the ideologies of most project managers, whose rankings of how much they enjoy doing things are, from highest to lowest: - Showing off optics bullshit like burndown charts - Adding features - Fixing extremely se…

It did not start good. You couldn't use keyboard to switch chats in the first year, or customize keyboard shortcuts...

I disagree. I didn't miss those features, and don't consider them to be must-haves in early builds. Yes, they took too long to implement them, but that's why I said it had a good start. As far as major features go, it was, in my opinion, the only app to get some of them correct (e.g. forced threading and the balance between customizability and overcomplexity in notification settings).

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

#787

Post by vel0city »

nikau wrote: post #751
vel0city wrote: post #696

Earlier quoted context omitted.

> I miss the days of just having a dedicated desk phone I don't really. It tied me to my desk. Now my extension is wherever I want to work, not just at my desk. Its on my cell phone, its on my work laptop, its wherever I am. Loads of desk phones didn't have any Bluetooth support so using a headset meant getting a probably expensive maybe proprietary thing with EHS support (or a mechanical handset lifter!!!). When I w…

Yeah its probably a half rose coloured glasses and half the era and implementation of deskphone. I had an pre-voip Avaya phone with 24 speed dials - for each contact it had a red/green LED next to the speed dial button that showed if they were busy. If it was green you could just press it and call. It had a proper headset port so no ghetto lifter :) Teams has available status also, but I find its pretty much useless…

Thanks for that URL tip, that'll come in handy.

Having more speed dial buttons would have made the desk phone a bit nicer to have. Some people in the office which used the phone a 10 speed dial buttons but a lot of the phones just had four buttons which one showed your cureent status.

Forward to cell is fine but it's only half the full feature of having your extension actually on your phone. You can receive calls, but placing them and having it show up as your office number is trickier. Our VoIP system eventually came out with halfway decent phone apps but it was a bit clunky how it actually worked internally migrating the presence from the desk phone or soft phone to the phone app.

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

#788

Post by PaulLeiby »

apecat wrote: post #700
kylen wrote: post #472

Earlier quoted context omitted.

Yup. It might even be that while the engineering team is aware of the faults, the MS exec team considers Teams to be brilliant. At the senior level the role becomes a sales role - you are continuously selling your output, team, product, vision, etc internally to the other execs, board, etc. It's important therefore to present whatever you are producing as exceptional. So you look for indicators that support your pitc…

Was looking for a good place to post this in the thread but I'll just drop it here. Microsoft Teams still lacks multi-account support on desktop. As in, you can't sign on to several business organizations like you can in Slack. It's so dumb and disqualifying. Utter nightmare if you work with several organizations. https://feedbackportal.microsoft.com/feedback/idea/c9995dc8-... I've bookmarked that page and I check in…

This is a problem even if you work for one organization (e.g. govt or university) but have clients/collaborators in other organizations, and want to join their teams.

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

#789

Post by leokennis »

roydivision wrote: post #379

My 2 cents of venting on this sorry excuse of software - Backtick formatting in a chat post only works after typing the closing backtick, deleting it, re-typing it - Text copied from a conversation is polluted with names and time stamps. "I really want this feature" said nobody ever - The mute/unmute button is hard to find, I don't think I've ever attended a Teams meeting without someone struggling with this. Teams s…

- When you paste a link and press enter to send, it doesn’t send immediately and instead sends randomly after a few seconds

- This means if you were typing a follow up message your messages will look like this:

> Hey visit this cool site: https://news.ycombinator.com/ It has al

>l these cool discussions about tech!

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

#790

Post by FastEatSlow »

naikrovek wrote: post #736
gorbypark wrote: post #308

Earlier quoted context omitted.

What is the “new” version’s tech stack? I always thought that with the Office and Windows team slowly adopting React Native for some features that they would redo Teams with that. Realistically they could start out with a React Native shell and just use web views for most functionality at first to replace Electron (and eventually, hopefully, rewrite some core functionality in RN and/or actually native bits).

.net native application per platform, with WebView2 views but logic moved to some .net language, probably C#. I believe all application logic is moving to .net with the visible elements being HTML & CSS, but do not remember where I read it, so take it with a grain of salt. if there was mention of react native, I do not remember it, but I gloss right over mentions of most web frameworks, so it may play a role.

It's surprising that nobody has mentioned that MS is calling this Teams 2.0. They're rewriting to React with WebView2. I don't believe any of the functionality will be in the C#, but we'll see.

It's probably worth me mentioning that I'm building a Teams client using Typescript and Tauri! https://opercom.co.uk

Post reply on HN