[deleted]
Ask HN: Why is Microsoft Teams still so bad?
531–540 of 814 posts
Re: Ask HN: Why is Microsoft Teams still so bad?
#532Re: Ask HN: Why is Microsoft Teams still so bad?
#533Amazingly I experienced a large MS shop choose Zoom over teams purely because they caught the MS salesperson lying about the Teams price.
Re: Ask HN: Why is Microsoft Teams still so bad?
#534Earlier quoted context omitted.
Throw JIRA into the mix while you're on it.
Wait, what's wrong with JIRA?
Subpar at what it's supposed to do, extra features don't add a whole lot, mostly made and configured for managers instead of developers. Largely the same reasons people dislike Teams. Has even worse integrations with the Atlassian stack than Teams with the MS stack.
JIRA, just like Teams, is slow, bloated, still won't fix basic issues and largely exists to appease managers. You have to actively work to make JIRA a pleasant experience. It's too easy for most management to make it hell.
Re: Ask HN: Why is Microsoft Teams still so bad?
#535Earlier quoted context omitted.
Don't forget the massive memory use, oh and now there's TWO versions of teams - one for 'work or school' accounts and one for other Microsoft accounts. What a great idea said nobody ever.
upvote for the two different teams, like wtf... also, there is no version that installs in a system directory (bad for deployment), and the deployment version is terrible (it downloads and installs teams every time a user logs in). requires tracking protection to be cut for microsoft websites on linux super buggy and unusable on linux
It's usable on Linux, I use it all day, every day. I just don't know why the Linux client is so far behind the web client despite being an electron app.
Re: Ask HN: Why is Microsoft Teams still so bad?
#536Earlier quoted context omitted.
Throw JIRA into the mix while you're on it.
Wait, what's wrong with JIRA?
I personally find that the more I have to use JIRA, and the more magical ephemeral rules that are set up in it to take actions in response to my actions with it, the more terrible it is to use.
I've worked on teams where I just threw info into a card, and it was acceptable to use, and I've worked on teams where commits had to have a JIRA tag associated or the commit got rejected, including in instances where bitbucket was timing out it's call to JIRA. In the latter cases, I prayed for Atlassian's swift destruction, but alas, was never answered.
So like a lot of tools, it's how you use it, mostly. That said, as far as universal problems, cloning cards has to be one of the worst UX experiences I run into on the job with any frequency that I can't just fix myself. If the web app needs to await a successful or failed clone of a record (or series of them), I'm not sure why they can't implement a modal or a spinner or other component to tell the user that something is happening, then either navigate the user to the new card, or ask the user if they would like to view the new card. Shooting off a process that you say could take an indeterminate amount of time then dropping eventually a completion notification and link in the bottom left panel is just about the least helpful way to communicate that information.
edit: unrelated meta comment, but it's funny as hell to me that this question got 4 replies in the few minutes it took me to write this reply, all within 10 minutes of the original. People are really out here just waiting for a chance to complain about JIRA. Myself included it seems. Makes me feel a bit bad, hate to pile on to popular sentiment when others have already commented in a similar direction.
Re: Ask HN: Why is Microsoft Teams still so bad?
#537considering how massive & varied the MS ecosystem is, kinda surprised it works as well as it does tbh.
for most biz/big orgs (MS bread-n-butter), good-enough pays the bills; non-functional requirements (speed, cool-factor etc) aren't much of a priority.
It's easier for IT deps at mid-to-big corps already invested in MS, wins on price, and connects well with MS infra (office, security/auditing etc).
With MS moving to Edge browser, their strategy looks interesting, and I think they will be solving much of their tech headaches (Teams, office etc) by shifting to mainly Web Technologies (even web3).
Re: Ask HN: Why is Microsoft Teams still so bad?
#538Earlier quoted context omitted.
Wait, what's wrong with JIRA?
I personally find that the more I have to use JIRA, and the more magical ephemeral rules that are set up in it to take actions in response to my actions with it, the more terrible it is to use. I've worked on teams where I just threw info into a card, and it was acceptable to use, and I've worked on teams where commits had to have a JIRA tag associated or the commit got rejected, including in instances where bitbucke…
I'm trying to cleanup a Git tree right now where people haven't put JIRA tags in their commit comments, it is impossible to find out why a change was made, it isn't a totally stupid requirement.
Re: Ask HN: Why is Microsoft Teams still so bad?
#539Earlier quoted context omitted.
Wait, what's wrong with JIRA?
Atlassian is an asshole company for their stance against selfhosting it.
What stance? You simply purchase a license and selfhost it.
See https://www.atlassian.com/migration/assess/compare-cloud-dat...
Re: Ask HN: Why is Microsoft Teams still so bad?
#540Teams doesn't have to be good to succeed. It just has to exist. It's not even very important how good it is. Given it exists, IT will make everyone use it on Microsoft's behalf regardless of how bad it is. Or another way to look at it is that the real customers for Teams are IT departments. It makes their lives easier because they don't have to do anything and it meets all the compliance requirements they are suppose…
Someone should make job board where people can filter out companies that use Teams instead of Slack or Discord.
Unfortunately, at least in my experience, if the company shows any signs of success then incoming Finance/IT execs will force a change to Teams to "enable growth". If they begin to struggle, then incoming Finance/IT execs will force a change to Teams to "consolidate and streamline". I've experienced both of these. Resistance is futile.