this post was submitted on 14 May 2025
233 points (99.2% liked)

memes

14737 readers
3020 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to [email protected]

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
233
"They" are on it 24/7 (lemmy.world)
submitted 1 day ago by [email protected] to c/[email protected]
11 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 37 points 1 day ago (5 children)

Serious question for anyone who knows about this sort of thing, new teams is an electron app right? Which from my understanding means it's basically just Chrome that only loads a single page? So how the fuck does it break so often!?

[–] [email protected] 11 points 20 hours ago

I work in the industry (not MSFT) on cloud reliability so I have insight.

  • The cloud itself is not as stable as some people may think. Standard is 99.9 % uptime. Which sounds great, but if your DB is 99.9 % and your compute is 99.9% and your storage is 99.9 % and your network and so on and any one of those going out breaks your application, then you don't have 99.9 % but (99.9 %)^n which is a lot less impressive. You can make things fault-tolerant through redundancy but that comes with great complexity which can cause outages of its own.
  • Apps like teams, like most B2B bullshit, provide added value by bundling together as much shit as possible. Chat, calls, calendar, spreadsheets, you name it. So now any one of those features going out individually can impact the whole app.
  • Every one of those features in the bundle is managed by a different team, possibly in a different country and coming from a different company acquisition. So now you have to glue unrelated tech stacks together which is super expensive.
  • The way you bundle things together in a SPA in a corporate environment with finite resources is by basically bundling together a bunch of iframes. Ever notice that the calendar tab on teams sometimes tells you to refresh your page to get new credentials? That's why, this fucking thing bundles its own authentication lib and barely talks to MS Teams so it can't properly refresh its tokens! If you like having one product's technical debt, now think about having 20 products' technical debt all conveniently forced to interact together in one web page!

Honestly I'm impressed by how well teams works with the very severe constraints they clearly have. Shit's got more moving parts than Ryanair's entire fleet and it only breaks once in a while.

[–] [email protected] 9 points 20 hours ago* (last edited 20 hours ago)

Because its backend is SharePoint.

[–] [email protected] 32 points 1 day ago

because it's a cobbled-together piece of intangible complicated software, that's gone through two major iterations for no good reason.

[–] [email protected] 7 points 1 day ago

Self sabotage

[–] [email protected] 4 points 1 day ago

I only ise teams for meetings on occasion for one external client, but it breaks this much when you open it up in the browser as well.