3 ms·

Teams is one of Microsoft's headlining apps right now, and it's been such a PR nightmare that they're explicitly advertising a major performance improvement, co

Teams is one of Microsoft's headlining apps right now, and it's been such a PR nightmare that they're explicitly advertising a major performance improvement, complete with a slick video (when was the last time you saw an everyday app do that?) So I highly doubt the people driving this initiative are just "unfamiliar with how to improve their software's performance". Something else is going on here: maybe they were saddled with something so bad it could only be fixed so much, maybe there's some technical hurdle we're just not appreciating, maybe it's an organizational problem (this is my guess). But Slack has a similar problem, so I doubt it's the first possibility (the 1.0 of the app just happened to be botched). There's something going on here Here's my wild uninformed guess: Teams has lots of features/integrations, and they're constantly expanding because it's in the limelight right now, so they've got too many engineers on it working on different features at the same time and not talking to each other enough. The system is now too sprawling to be considered (or optimized) as a whole, which means there's tons of redundancy and toes-stepping going on. Shipping the org chart, etc. (Ask me where this vivid picture came from)

saagarjha 4y ago
I suspect (obvious disclaimer, this is speculation, but I've seen this happen many times elsewhere) is that the Teams team (heh) was asked to improve their performance for this sprint and they poked around a little bit to find some of the easiest wins, which is what we're seeing here. At most places, presenting that you've improved launch speed by over 2x is a major success, and their PR team decided it was worth advertising. The people who worked on this should be proud of the work they did but there is still clearly a long way to go to improve the app's performance.
- seadan83 4y ago
  This rework has been in the works for some time, they released a whole blog post explaining some changes (eg, switched from angular to react, and more): https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/27/welcome-to-the-new-era-of-microsoft-teams/ https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/2...
908B64B197 4y ago
> Something else is going on here: maybe they were saddled with something so bad it could only be fixed so much, maybe there's some technical hurdle we're just not appreciating They started with Electron, and are now moving to WebView2. When the project started Edge was still not Chromium based (it was the IE fork) so they couldn't even use that.

saagarjha 4y ago

I suspect (obvious disclaimer, this is speculation, but I've seen this happen many times elsewhere) is that the Teams team (heh) was asked to improve their performance for this sprint and they poked around a little bit to find some of the easiest wins, which is what we're seeing here. At most places, presenting that you've improved launch speed by over 2x is a major success, and their PR team decided it was worth advertising. The people who worked on this should be proud of the work they did but there is still clearly a long way to go to improve the app's performance.

seadan83 4y ago
This rework has been in the works for some time, they released a whole blog post explaining some changes (eg, switched from angular to react, and more): https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/27/welcome-to-the-new-era-of-microsoft-teams/ https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/2...

908B64B197 4y ago

> Something else is going on here: maybe they were saddled with something so bad it could only be fixed so much, maybe there's some technical hurdle we're just not appreciating They started with Electron, and are now moving to WebView2. When the project started Edge was still not Chromium based (it was the IE fork) so they couldn't even use that.