(It really is amazing how much Teams has lit up "we have the ability to do that now" for SharePoint features that have existed almost forever. I was particularly amused when someone asked me why so many Teams features have SharePoint URLs when SharePoint didn't support them and then showing them the three or four step process to do it on SharePoint that has been there all along.)
It's great for ad hoc groups of people to chat or for direct chat. It's also great for meetings. Where it gets cumbersome is in the persistent chat room management.
And as someone who is not a fan of chat rooms as a replacement for emails (I can't even filter or categorize information) I'm glad about that part.
I’ll take that in return for it not trying to replace email, which, at the very least has folders, and rules, and starring (nearly every implementation has some version of this), multiple clients, the ability to access from non GUI clients, etc.
I really don’t understand at what point we decided that email sucked and really what we needed was a proprietary solution that are up a ton of RAM and hardly had any ability to customise or optimize in ways thateven non technical people have successfully managed wth email.
For all the non email like features, I.e. instant chatting with an individual, or a group of people, Teams works great.