3 ms·
I used to think teams was OK (the audio is seriously great), but now I have a use for my RAM, and while idle, it consume twice as much RAM as a plain Firefox, a
by orwin 3y ago
I used to think teams was OK (the audio is seriously great), but now I have a use for my RAM, and while idle, it consume twice as much RAM as a plain Firefox, and more than a wsl running vscode. This is abnormal.
- jug 3y agoNote that Teams was using Electron but a preview no longer bundles a browser and massively reduces RAM usage. Still only for Windows though.
- cmehdy 3y agoIt also has an endless list of visual glitches, hardware issues even with "headphones recommended by Microsoft", input issues, pretty bad UX, poor integration with Microsoft's own services (SharePoint, outlook calendar..), a horrible "test call", etc. Doesn't seem to matter anyway, once a Windows shop is captive they know most clients are there for life..
- bdavbdav 3y agoAudio device selection is horrible. Several of my (otherwise fully working) devices either don’t show up in the lists, or if they do, pass no audio.
- pluijzer 3y agoThe most annoying to me is that the elapsed time element doesn't have a fixed size. It constantly changes size and pushes all other elements from left to right. It is very distracting. I can thing of so many easy fixes for this yet it is there since at least 3 years. This comes across as very amateurish for a product of a multi billion company.