That’s all.

EDIT: Thank you all for detailing your experience with, and hatred for, this miserable product. Your display of solidarity is inspiring. Now, say it with me:

Fuck Microsoft

  • sugar_in_your_tea@sh.itjust.worksEnglish
    3·
    18 days ago

    Yeah, I have a similar experience, but it certainly lacks in features compared to other messengers. For example:

    • chat - formatting is terrible, Slack is way better here
    • groups - haven’t bothered figuring them out, in Slack making a channel or group message is super natural
    • resources - Teams eats RAM like crazy, Slack seems to be a bit more respectful
    • recent chats/messages - I can never find what I’m looking for, with Slack it’s simple

    I like the integration w/ Outlook because we’re basically forced to use it at work, but Slack is way better for almost everything that doesn’t interact directly w/ Outlook. So if it’s not a scheduled meeting, I and my team much prefer Slack.

    • SayCyberOnceMore@feddit.ukEnglish
      3·
      18 days ago

      Gotta say, formatting of text isn’t a high priority for me… I’m pinging someone about a thing, I’m not writing a presentation. Adding emojis is about as much as I need 🤔

      And - to me - adding people to an adhoc group call / chat is straight forwards - and finding those conversations later is too

      But, I believe that there’s a few Corp IT settings that can be adjusted (we’ve recently lost the ability to add gifs for example), so maybe that’s what’s going wrong.

      But we’re a long way from AOL IM 😉

      • sugar_in_your_tea@sh.itjust.worksEnglish
        4·
        18 days ago

        I send code snippets, quote sections of linked documents, and provide in-line links pretty often, kind of like here on Lemmy. Slack isn’t as nice as Markdown, but it’s good enough, whereas Teams is a complete pain in in the butt and it completely butchers code blocks. That said, I’m a team lead, so I fairly frequently post about recent releases, security issues, or give cliff notes of recent meetings, so formatting for me matters quite a bit.

        And for calls, we have multiple logical groups of people, such as:

        • development teams
        • team leads (for all teams)
        • groups by location
        • groups by role (developers, QA, etc)
        • release groups - may be part of a team, multiple teams, or parts of multiple teams
        • automated alerts when prod has an issue

        And we have ad-hoc group chats where just a handful of people need to be involved, but they don’t fit cleanly into one of the established groups above (e.g. project manager wants to know a rough estimate for an upcoming project).

        Teams works fine, but I find it annoying to use.

        • lud@lemm.eeEnglish
          1·
          18 days ago

          Have you used teams for sending code recently?

          I tested it last week and it worked pretty well and even featured syntax highlighting. From the very limited one time test I actually prefer the way teams handle code since it doesn’t force you to use some kind of snippet.

          Teams is also supposed to get better formatting and chats fairly soon. I will continue to use slack because I prefer it but it’s nice that teams is at least getting better.

          • sugar_in_your_tea@sh.itjust.worksEnglish
            1·
            18 days ago

            Yeah, it has gotten better since a year or so ago, but it still falls quite a bit short of Slack. Slack can do snippets or not, it’s up to you.

            And yeah, it’s nice that it’s getting better, especially since I’m forced to use it for work (and interviews, where bad code handling sucks).

            • lud@lemm.eeEnglish
              1·
              18 days ago

              You can do regular code blocks in Slack? I thought you only could do inline or in snippets.

              We luckily use both at work.