I am resigned to the fact that some of my requirements really do mean I need a Ryzen 7 with 16GB of RAM. Sadly my biggest compute loads are for MS Teams and webmail.
I am resigned to the fact that some of my requirements really do mean I need a Ryzen 7 with 16GB of RAM. Sadly my biggest compute loads are for MS Teams and webmail.
I really do empathize here, after having to use Teams for around 2 years. It's amazingly slow, confusing, buggy (it would crash the tab quite regularly), and just generally a perfect role model for what software shouldn't be[0].
I'm still quite amazed that Microsoft decided this was acceptable. I'm curious how Slack performs; perhaps they're not trying harder because there's no[t much] competition in this space ...?
[0]: (If I remember correctly, they were using AngularJS at the time, but I'm sure they're now using the regular React stack.)
> I really do empathize here, after having to use Teams for around 2 years. It's amazingly slow, confusing, buggy (it would crash the tab quite regularly), and just generally a perfect role model for what software shouldn't be[0].
Teams for Linux [1] also struggles with resources. Teams in general is an absolute mess. I would go further and say that most MS products are resource intensive buggy crap.
https://techcommunity.microsoft.com/t5/word/word-online-web-...
https://answers.microsoft.com/en-us/msoffice/forum/all/how-t...
https://answers.microsoft.com/en-us/msoffice/forum/all/why-d...
https://answers.microsoft.com/en-us/msoffice/forum/all/word-...
https://answers.microsoft.com/en-us/msoffice/forum/all/text-...
https://answers.microsoft.com/en-us/msoffice/forum/all/text-...
https://answers.microsoft.com/en-us/msoffice/forum/all/word-...
https://answers.microsoft.com/en-us/msoffice/forum/all/when-...
https://answers.microsoft.com/en-us/msoffice/forum/all/word-...
https://answers.microsoft.com/en-us/msoffice/forum/all/why-i...
I have no idea how many engineers work on Office Online, but other than security bugs I cannot think of a more important issue to resolve.
- Non of them are close to feature complete. As soon as you have to do more than chat (share files, do meetings, etc) they will let you down.
- In most corporate environments there is some extra layer of authentication involved I highly doubt these clients are able to handle.
The best way I have found to have a lighter teams experience is to simply use the web version as a PWA. This basically offers you all the features without the extended footprint of effectively running a second browser.
I kinda have to ask, what features can you enforce in rate limiting in a first party client that you can't enforce in a third party client?
My colleagues and myself used Slack for years, were forced to use Teams for about 2 years because of our new parent company, and finally went back to Slack after we collectively quit that shitshow to start a new company.
While Slack isn't perfect either, it's miles better.
We switched from HipChat to Google Chat, which in my mind is pretty bad. Customers are often on Teams, which somehow manages to be MUCH MUCH worse. People kept telling me that Slack is much better than either Google Chat or MS Team, but after using it I can't say that I'd agree. Teams is clearly the worst, Slack is awful in its own way and Google Chat manages to be the best of the three, but mostly because the two others are so terrible.
It's clearly not an easy problem to solve, but I do wonder why all of these "enterprise" messaging/meeting/chat platforms are so terrible.
Their customers find it acceptable so it's OK for MS too.
If customers wouldn't find it acceptable they would use something else and we wouldn't be having this conversation. Maybe it helps that it comes with the Office suite and they already paid for it.
By the way, when a customer asks me how I want to do a video chat, almost always with screen sharing, I suggest Meet. If they mandate Teams, OK, I'll do Teams in a browser. Actually the best screen sharing seems to be Skype. It can zoom too. None of them can go full screen with no useless UI around the shared screen, tough luck. None of my customers are using Zoom anymore.
It also highly depends on what you want to browse. HN for example will work just fine without much memory. Expecting YouTube to be as light as 90s websites is asking a bit much.
Having said that, I do agree that we have overshot, and many websites are way too heavy for their use case.
Sticking with YouTube as an example, assuming for a moment that whatever device you are using does have hardware decoding, so video playback isn't dragging down performance. It still is an extremely heavy website due to all the tracking shenanigans, interactive elements and the fact that it is an SPA based design. Alternative front-ends like invidious show it is possible and in the past Google did actually provide light versions of many of their web apps specifically for this sort of use case. Sadly that is no longer the case.
- Tried creating a new blank Waterfox profile with no changes except uBlock0. It drops frames, and the borders of the video (4:3 pillarboxes on a 16:9 screen) have a blue or green tint after I seek.
- Same result in a new blank Firefox ESR 115.6.0 (last Windows 7 release) profile with uBlock0.
- The YouTube embed player at https://www.youtube.com/embed/lEuHOFgjrAo, on my main Waterfox profile, runs as smoothly as Invidious (no stutters unless I'm interacting with the player UI).
qutebrowser and nyxt would fit the bill better. to be honest I feel like nyxt is really cool, but I'm not sure if choosing a lisp was the right idea.
So one could use it on a machine that did not even have any desktop enviroment installed.
Search on webmail is instantaneous. It was not on MTAs last time I tried. I remember someone always struggling to find old mails with his MTA while gmail would find it quite quickly.