MS Teams 2.0 – trying to fix the issues
windowscentral.com
windowscentral.com
How do people deal with Teams' vastly inferior chat after coming from Slack or Mattermost or anything else remotely modern?
Teams supports inline and multi-line code blocks using Markdown formatting. I can't try it ATM, but does that not work as it does in Slack?
I ran into this one constantly. And lately when I paste something in and set the paragraph type to monospace, it puts a box around every single line! I've tried using the code snippet thing, but that adds so much padding and insists on adding a title. I've kind of given up on trying to make code or terminal snippets look okay in Teams.
It's frustrating that a company with as many developers as MS has can't seem to get this right. Do they not dogfood Teams? Whatever happened to "Developers! Developers! Developers!"?
Also, tab and shift+tab seem to work to indent and unindent, for sub-lists.
they want (they REALLY want) to allow users to copy from Teams and paste into Teams as RTF and many of their design decisions revolve around this decision. when you type markdown formatting cues into Teams they get converted to RTF which is why it's such a pain (or simply impossible) to edit something at either end of a specially formatted bit of text.
maybe they've undone this stupidity in teams 2.0 but their love of backwards compatibility tells me "no," very loudly.
All I can say is hold your praise.. :(
I'm an engineering manager at a multinational company, which also have remote employees.
Half a year ago, we got a new Director of Engineering, who decided to move from Slack to Teams, due to compliance implementation.
No one in the engineering teams want to use Teams at all; they deal with it by secretly having a Slack Team that only they (as far as they know, at least) know about.
While the rest of the company is forced to use Teams, the engineers are using Slack as they've always been doing.
Not surprising to see it suck so bad in Teams.
Their "own" edge WebView2 tech is powered by chromium, the same as what powers the old electron.
And "based on react not JavaScript"... React is a framework in JavaScript.
Neither are fundamental improvements. They're more branding than anything.
None of these explanations make any sense. What would make sense is if their team stops prioritizing glossy new features and optimizes the core code. Just like the VS Code team has done from the very start.
Perhaps this is what they are doing and they're trying to peddle their WebView in the process. If it's just those 2 changes they mention I'm sure the result will be underwhelming. As always with Teams so far.
Performance and resource usage are my two biggest issues with Teams so this is a welcome update. I don’t think Teams is perfect, but it is useful for what it is and generally is good enough.
Inability to handle formatting of messages is a big one. It will decide that my codeblock should actually be two, and it is impossible to merge them.
Scrolling in opposite directions depending on the tab.
Making up another SharePoint site with each group team chat so that we can ensure we silo our data and never find it again.
Right now everything is JavaScript. Shh! I’m talking! I said everything! To the point that getting a non-SPA code sample for Azure Identity is a serious research exercise. That Visual Studio will deploy a blank ASP.NET project that has mostly JavaScript in it. And so on…
so when people on youtube say ipad better because battery life and noise. how much teams was root cause of harm to surface sales?
"There is no problem in Windows that a reboot cannot fix"
"There is no problem in Windows that a complete reinstall cannot fix"
Call me skeptic.