back
28 comments
It’s just funny (or sad actually) that Microsoft apparently won’t eat its own .NET MAUI dog-food, even for such a simple application.
WebView2 and React FluentUI are also Microsoft's own dog food. As much as anything it is a competing choices thing for them.
Teams works in the browser, but MAUI doesn't. Also, MAUI didn't exist when Teams was invented, and they had only just acquired the Xamarin company.

MAUI is great, and they should invest more in it. WebView2 and MAUI work together well.

This is probably a good future direction.

> MAUI is great

Who has or is using it to build cool, robust, or otherwise interesting things?

> MAUI is great, and they should invest more in it.

Hence Teams would have been a fantastic showcase for it.

If not Teams for reasons discussed here, just anything of note would be a good trust-signal for CTOs.

I don't think it is likely.

You'd also have to re-educate the entire Team's Dev. Team on using C# for development, away from the web stuff they've been doing.

I think it totally makes sense to stick with web

Or, replace them with a team that already knows C# - which I assume should be possible at Microsoft- and also knows what they’re doing.
A rewrite would be very expensive, and this already works. Microsoft also invented TypeScript and WebView2. They are eating their own dogfood.
sure, ms has hundreds of teams of C# developers just sitting around doing nothing while they look for products to take over..
Apparently the teams tab and the chat tab are still two different things.

How can it be that no one is pissed how stupid this is?

Wtf I just want to be able to have all critical things one one fucking window and not needing to switch forth and back...

Aargh

It's not even just an annoyance in the having-to-click-between-tabs sense. It makes channels nearly useless because everyone is normally in the chats tab, so no one is keeping up with what's going on in channels. Meaning the only way to get people's attention is to noisily ping everyone, which most people don't want to do so barely anyone posts in them.
My company has given up on the teams tab and only uses private group chats, due to the terrible UX. We have ~15 persistent group chats for a company of ~20.

Not good for keeping everybody in the loop, since somebody is almost always left out, but not much I can do at this point.

Chats are ad hoc watercooler talk across arbitrary sets from everyone.

Teams+Channels are persistent permissioned shared (team and squad scoped) email threads with backing file store.

I hate this so much but never quite put my finger on it. Thank you.
> Wtf I just want to be able to have all critical things one one fucking window

...it is one fucking window

In one Tab...
These modifications appear to be excellent ones. The entire Office 365 gimmick is very popular at my company. I suppose it would really free a lot of people from the awful Microsoft Experience they are currently experiencing.
> I suppose it would really free a lot of people from the awful Microsoft Experience they are currently experiencing.

If Microsoft was not able to do this until now since 20 years, i don't think they are able to do it.

Hopefully they remove the ability to accidentally call 30 people in a chat without warning.
I have dozens of reasons I hate MS Teams. Having Ctrl-Shift-C start is top of that list.

The number of times I've been copying a code snippet out of a chat into a terminal and accidentally started calling the other person is way too high.

teams is already a slow buggy mess that crashes multiple times a day for me with many features not working, this is before I even get into the poor UI design. Moving to react is just going to make things worse. Really trying to convince my manager to stop forcing us to use it.
They highlight where its performance was improved by the changes made. Are you refuting that?

Today, React can be a wise decision.

right trusting microsoft sounds like a great idea, just like when they bought github. last time i heard them say that the app actually boots up faster and is faster on average but anytime I need to send a file or do a screenshare or join a meeting it crashes if I'm unlucky, if I'm lucky it will just slow down and everything lags. It's not just me either, everyone on my team and even our client who joins in on our teams meeting runs into the same issue. Our solution for them is to actually join meetings via browser.
They’re moving from AngularJS to React. That seems unlikely to make things worse.
> They’re moving from AngularJS to React. That seems unlikely to make things worse.

Famous last words.

Teams has never crashed for me. I hassled IT to get me in on the preview, and it's hundreds of MB of RAM lighter than the old app.
new architecture looks dope. i'm sure performance is going to be better than using electron. let's wait and see how it will be for people running the app in the wild.