5 ms·

From what I can tell, it's written in Electron. I assume they did this so that they could share the code base between desktop (win/mac), ios/android/winphone, a

From what I can tell, it's written in Electron. I assume they did this so that they could share the code base between desktop (win/mac), ios/android/winphone, and web -- keeping the features sets the same on all platforms. VS Code is the same way and that works beautifully on Mac. I expect that same for this. Disclaimer: I work for Microsoft (Azure) but have no relation to Office or Microsoft Teams.

dmode 10y ago
It is not about the technology platform. You still have to dedicate resources to ensure feature parity across both OS systems. When MS starts selling Teams to huge enterprise customers (e.g., Walmart, Ford, GM etc.) that are on 99% Windows platform and the feature request and pressure starts building, where do you think the resources would go ? It is not MS fault, it is the nature of their business. Windows based enterprises are their bread and butter and that's what they will prioritize. I work for an enterprise Cloud company, and we prioritize IE because of this reason.
- Ant5do 10y ago
  I don't think you know how Electron apps work. http://electron.atom.io/ http://electron.atom.io/
- Analemma_ 10y ago
  > It is not about the technology platform. You still have to dedicate resources to ensure feature parity across both OS systems It is about the technology platform, because the amount of resources necessary to ensure feature parity is a function of the platfrom. Word for Windows and Word for Mac are probably two separate giant monsters of early-90's C++ and keeping them in sync is agony. Assuming Teams is written in Electron, the amount of work is nowhere near the same; not having feature parity across operating systems is probably harder than having it.
  - golf1052 10y ago
    Word for Windows and Word for Mac are much closer together than you may realize. Pretty interesting talk about cross platform Office. Part 1: https://www.youtube.com/watch?v=3HROqnw-nf4 https://www.youtube.com/watch?v=3HROqnw-nf4 Part 2:https://www.youtube.com/watch?v=MGMoRu5yrVc https://www.youtube.com/watch?v=MGMoRu5yrVc
    - Analemma_ 10y ago
      Ah, interesting. I always just took it for granted that the old Office codebases were huge beasts, but maybe not. Thanks for the info! Still, no matter how nice that codebase is, I assume they can't beat Electron for ease of X-platform compatibility.
lawnchair_larry 10y ago
Electron is complete shit, especially for long running processes. Might as well use the browser version.
- mmusc 10y ago
  seems to be working just fine for visual studio code
- cududa 10y ago
  Perhaps it's just the people writing electron apps doing Abbas job, because some of them work fine

dmode 10y ago

It is not about the technology platform. You still have to dedicate resources to ensure feature parity across both OS systems. When MS starts selling Teams to huge enterprise customers (e.g., Walmart, Ford, GM etc.) that are on 99% Windows platform and the feature request and pressure starts building, where do you think the resources would go ? It is not MS fault, it is the nature of their business. Windows based enterprises are their bread and butter and that's what they will prioritize. I work for an enterprise Cloud company, and we prioritize IE because of this reason.

Ant5do 10y ago
I don't think you know how Electron apps work. http://electron.atom.io/ http://electron.atom.io/
Analemma_ 10y ago
> It is not about the technology platform. You still have to dedicate resources to ensure feature parity across both OS systems It is about the technology platform, because the amount of resources necessary to ensure feature parity is a function of the platfrom. Word for Windows and Word for Mac are probably two separate giant monsters of early-90's C++ and keeping them in sync is agony. Assuming Teams is written in Electron, the amount of work is nowhere near the same; not having feature parity across operating systems is probably harder than having it.
- golf1052 10y ago
  Word for Windows and Word for Mac are much closer together than you may realize. Pretty interesting talk about cross platform Office. Part 1: https://www.youtube.com/watch?v=3HROqnw-nf4 https://www.youtube.com/watch?v=3HROqnw-nf4 Part 2:https://www.youtube.com/watch?v=MGMoRu5yrVc https://www.youtube.com/watch?v=MGMoRu5yrVc
  - Analemma_ 10y ago
    Ah, interesting. I always just took it for granted that the old Office codebases were huge beasts, but maybe not. Thanks for the info! Still, no matter how nice that codebase is, I assume they can't beat Electron for ease of X-platform compatibility.

lawnchair_larry 10y ago

Electron is complete shit, especially for long running processes. Might as well use the browser version.

mmusc 10y ago
seems to be working just fine for visual studio code
cududa 10y ago
Perhaps it's just the people writing electron apps doing Abbas job, because some of them work fine