How do people deal with Teams' vastly inferior chat after coming from Slack or Mattermost or anything else remotely modern?
How do people deal with Teams' vastly inferior chat after coming from Slack or Mattermost or anything else remotely modern?
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 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.
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.
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?