That’s all.

  • Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 month ago

    We used to use it before switching to Google Workspace (don’t get me started on how much I hate that), and Teams wasn’t too bad. But it had two things going for it then:

    • It was replacing Skype for Business which never should existed because it was so awful. Compared to SfB, literally anything was an improvement.
    • At the time, it was basically a Slack clone that didn’t have everything and the kitchen sink bolted on yet and was decently lightweight if you used the browser version.
    • NegativeNull@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      Out of the frying pan and into the fire!

      To be fair, you are right about SfB. My previous job used that

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        1 month ago

        Maybe I’m remembering early/beta Teams with rose tinted spectacles, but at the very least the silver lining was that I no longer needed to keep a separate Windows machine running just for work IM.

        I even tried adding it to Citrix, but it refused to install on a server version of Windows.

    • spamfajitas@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      I’m still convinced the turning point was when Microsoft deprecated Skype for Business and merged the devs from that team with the ones working on Teams. My tinfoil hat theory is they brought their garbage Lync code with them and pulled seniority to somehow jam it into the new codebase.