Also teams has this arbitrary message character limit that makes it terrible for sharing large chunks of text (partial logs for example).
While the integrations with outlook (mail/scheduling) + teams works “well enough”, the experience of the app itself leaves something to be desired.
(But I too wish plain text pasting was the default more often.)
Even if it had, they might have made it the default, either to show of that styles copied over, or for consistency. If you paste a picture, you don’t lose formatting, either (of the picture, whatever that means, or any text in the image)
If you copied some text in MacWrite, for example, exited MacWrote, launched MacPaint, and ⌘V-ed into MacPaint, you likely wanted to keep the font, size and style.
Some programs also have several variants of “without formatting”. Excel is a good example (https://support.microsoft.com/en-us/office/paste-options-8ea...). Which one should be the default?
e.g. copy a jpeg file and you can paste it into Slack, and it will automatically add the image to the post. Paste it into the terminal and you'll get the absolute path to the file. Those sound like sensible defaults that are essentially 'context sensitive paste'.
You could copy a link from a webpage and store both the HTML version and a raw-text version in the clipboard, probably a version that used an annotated string, too.
For the same reason, yeah... this isn't as intuitive when it comes to software like Excel.
Most of those are very specific versions of formatting or specialty features.
The only ones that would qualify as "paste without formatting" are "formulas" and "values" modes, and of those two I'd probably say "formulas" is a better default.
I'm not sure how intuitive that would be for users, though, having different defaults depending on where the data is coming from.
- Normal users often prefer to paste with formatting.
- Normal users will never figure out how to do that if it's not the default.
- Normal users will usually reluctantly accept paste-with-formatting even if it's not what they wanted—that is, it's only rarely entirely unacceptable for them.
- Power users will figure out how to paste without formatting.
More likely they were just worried Slack was attacking their enterprise segment and killing Skype so they rushed a shitty product to market ASAP. "Embrace, extend, extinguish" has turned into "panic, copycat, repeat".
But that behaviour everywhere would drive me nuts.
Your use case will not suffer since whitespace is text.
I've had countless other examples over the years where "paste without formatting" involved lots of manual editing of white space. Bullet and numbered lists sometimes vanish which rather matters if the text says "see point 3 above"
Definitely a helpful shortcut!
https://www.makeuseof.com/tag/copy-paste-text-without-format...
As an extra measure I configure the macro to automatically type the text and not use the direct clipboard paste. This takes care of the situations were the app prohibited pasting.
That's just Microsoft.
I can probably count on one hand the amount of times I've wanted to actually retain source formatting. But, it's the default option on almost any microsoft product out there. And, apparently, on Teams it's not an option at all.
This has been known since 2016 at least https://microsoftteams.uservoice.com/forums/555103-public/su... "Support for multiple work accounts is still being worked on and will come at a later date."
Also opening docs and excel sheets inside the main window by default and blocking chat while doing it is absolutely atrocious.
Someone built these features. Why are you building a feature on who can attach images?? The entire mindset is completely wrong and comes from an overcontrolling enterprise mindset completely incompatible with what we expect from a chat tool.
Oh and every time I log in Teams asks whether it can control my entire device. No.
This is the root of all Teams fuckups.
It's an asinine primitive mapping, that could only come from a project manager who spent their entire career optimizing SharePoint access controls to meet HR product requests.
The entire point of modern chat solutions is persistence and searchability. So the only real differentiation should be public or private channels.
Then they rolled out Teams for the whole company. We lost a ton of features that made Mattermost a delight to use. The way channels worked felt less intuitive, and it was just harder to care about group messages. And the worst part? A 30 day deletion policy.
The solution for us was to create multi-user chats in the "Chat" section and let the "Teams" section die the horrible death it deserves.
The notifications are more consistent in "Chat". But god forbid someone talks too much, because then you get those horrible non-native notifications that are completely broken in itself too.
It's probably the worst app I've used in years, and that's saying a lot because app quality is incredibly bad these days.
If not even Microsoft itself writes native code for their own bloody OS then we're just doomed. It's just all so sluggish.
I agree a native client would be great, although I assume this choice is more because Microsoft wanted it to be multi-platform across iOS, Android, Web, Mac, Linux, Windows, Chromebook e.t.c. and that would either require building it multiple times, or building it in html/js as the lowest common denominator (web).
https://support.microsoft.com/en-us/windows/silverlight-end-...:
“Microsoft Silverlight will reach the end of support on October 12, 2021. Silverlight development framework is currently only supported on Internet Explorer 10 and Internet Explorer 11, with support for Internet Explorer 10 ending on January 31, 2020. There is no longer support for Chrome, Firefox, or any browser using the Mac operating system.”
So you mean the Lync codebase.
That's a pretty low bar to start with.
As one "for example", that's the product team that couldn't figure out how to stop repeating AD logins with invalid saved passwords for 5+ years. Which invariably led to a system you were signed into somewhere locking your account every password rotation.
For VC and file collaboration Teams seems good in absolute, for messaging it seems good only relative to that. Messaging feels like a third-priority feature in Teams. If you're coming from a good messaging experience and that's what you mostly use Teams for then it's no doubt a really poor experience.
Agree with your sentiment except that it's not Teams fault that your client didn't care about message history when they decided to migrate to Teams.
There seems to be no way to open or see the meetings directly within team. I always have to open my mail, click the link, go to the website, click on open in teams and only then will it open the meeting.
Easily my least favorite chat app, save for those that break basic functionality as their core product (Snapchat). Teams doesn't seem to understand that organization admins might want to see user names in a different format than users. Everyone's name is Last, F., which makes sense from an administrative standpoint but needing to click into someone's profile to figure out who they are gets old _very_ fast.
The only selling point that Teams seems to have is "we're already paying for it."
Welcome to another walled garden messaging service! At least lessons were learned..not.
Company decides the most important thing is to save $20 a month on not paying for slack
Our company (we'll call it Monsarno) was bought by a certain German aspirin company, and our Bavarian overlords are slowly forcing us from Slack over to Teams. It's a nightmare, and very few groups have made the transition willingly.
Client dropped Slack for Teams. I hate it, and information exchange has dropped precipitously since everyone switched. So slow, half the time text markup doesn't work, and the UI is inconsistent depending on if you're typing in a chat, meeting, or channel.
Oh and none of the Slack logs were kept, losing years of information. (But that's not the fault of the Teams software)
I loathe Teams.