Screen-sharing on Teams has been pretty solid -- after all, screen sharing is an enterprise's bread and butter. As someone who averages 10-15 meetings a week, most of them with screen shares, I think I have a pretty good sample size to come to that conclusion.

I can't comment on aesthetics since that's fairly subjective. I can't comment on integrations either since I've only tried a few, but I find it integrates fairly effortlessly with Azure Devops (ie Microsoft's attempt at replicating Github in what was previously Team Foundation Server) [1].

Here's the thing about Microsoft stuff -- generally things work well if you remain in the Microsoft ecosystem. Otherwise, you'll likely have to do extra work.

That said, Teams has improved drastically since 2017. Microsoft's philosophy these days seems to be move fast, ship crap and get better quickly. Not in every product line, but I've definitely seen this happen with Teams development and I've actually come to like what the Teams product has become today. I have to confess, Microsoft under Satya Nadella is a very different company from what it once was.

[1] We're not allowed to use Github in my organization (bigcorp, IP etc.) but I've found Azure Devops to be quite a decent substitute. It plays well with a git pull-request workflow, has almost full feature parity with Github as far as I can tell, plus has a built-in kanban board.

I like Github -- it's more tightly focused and simpler -- but I've been able to carve out a part of Azure Devops that is similar to Github and maintain my previous git workflow without much trouble. Azure Devops is not the dumpster fire I'd expected it to be -- it's actually fairly good in parts.

(the only pain-in-the-neck with Azure Devops is licensing cost -- it's not free. In the enterprise, it has named-user licensing which can get costly. I wouldn't have used it if we didn't already have it and couldn't use private Github.)