4 ms·

This is the most Microsoft error message I have ever seen

by klysm 2y ago

fragmede 2y ago
This message will delete itself after this. Please save its contents if you with to retain it.
m463 2y ago
Wouldn't a more microsoft message be about competing products failing to exist? I've seen teams messages on firefox and safari about features not existing "download the teams native app!"
- beefnugs 2y ago
  More microsoft would be a 5 minute message on screen promising that they have never and will never misplace any of your messages, right before this monstrosity appears
frankthepickle 2y ago
task failed successfully!
uyzstvqs 2y ago
Only for a while until someone changes it to "Something went wrong"
- 2four2 2y ago
  With a large :( to redundantly communicate that something bad happened, in case the user didn't even read the simplified message.
- caseyy 2y ago
  Don’t forget “Oops!” — the element of surprise. The developer doesn’t know what went wrong and things definitely don’t go wrong all the time at Microsoft! This is as surprising to the developer as it is to you! It’s also pleasantly humane, not like “ERROR:”, meaning it’s more of a silly and fun oopsie doopsie than a systems engineering failure. Don’t you just feel better as the user seeing that? It’s not the systems engineer’s fault and neither is it yours. It just kind of happened. What even is “it”? No one knows! Computers are weird — eh? Nothing like a whimsical hiccup in your computing to brighten the day. Whatever you were doing, whether it’s saving work, buying something, or completing critical forms, some of that was probably done, or maybe not, but who really knows? Hehe, not us — we are just as surprised! Oh, and don’t call support with this stuff. There’s not enough to go on even if you reported it for us to investigate. It’s just one of these things, you know? Forget about it and move on buddy! You’ve got an essay to rewrite/a purchase to figure out/a critical form to complete again, and who knows what will happen then! Will it go through? Maybe, maybe not. It will be surprising if it doesn’t! Isn’t it just so exciting?
  - IshKebab 2y ago
    Damn straight. This came up in an earlier discussion about languages that rely heavily on exceptions - they sensibly don't want to expose backtraces so you get this `try: response_handler() except: print("oops!")` nonsense because the programmer literally doesn't know what went wrong and they're sure as hell not going to give you the details. I find it as infuriating as you.
smrtinsert 2y ago
Fatal Error: Operation completed successfully.
consumer451 2y ago
SharePoint is supposedly one of the keystones of Microsoft. The answer to "how can I find all SharePoint Sites where I am a member?" is: > Search SharePoint for contentclass:STS_Site How is this, and op, cluster f possible? How do these decisions get into prod?

This is the most Microsoft error message I have ever seen

by klysm 2y ago

This is the most Microsoft error message I have ever seen

fragmede 2y ago

This message will delete itself after this. Please save its contents if you with to retain it.

m463 2y ago

Wouldn't a more microsoft message be about competing products failing to exist? I've seen teams messages on firefox and safari about features not existing "download the teams native app!"

beefnugs 2y ago
More microsoft would be a 5 minute message on screen promising that they have never and will never misplace any of your messages, right before this monstrosity appears

frankthepickle 2y ago

task failed successfully!

uyzstvqs 2y ago

Only for a while until someone changes it to "Something went wrong"

2four2 2y ago
With a large :( to redundantly communicate that something bad happened, in case the user didn't even read the simplified message.
caseyy 2y ago
Don’t forget “Oops!” — the element of surprise. The developer doesn’t know what went wrong and things definitely don’t go wrong all the time at Microsoft! This is as surprising to the developer as it is to you! It’s also pleasantly humane, not like “ERROR:”, meaning it’s more of a silly and fun oopsie doopsie than a systems engineering failure. Don’t you just feel better as the user seeing that? It’s not the systems engineer’s fault and neither is it yours. It just kind of happened. What even is “it”? No one knows! Computers are weird — eh? Nothing like a whimsical hiccup in your computing to brighten the day. Whatever you were doing, whether it’s saving work, buying something, or completing critical forms, some of that was probably done, or maybe not, but who really knows? Hehe, not us — we are just as surprised! Oh, and don’t call support with this stuff. There’s not enough to go on even if you reported it for us to investigate. It’s just one of these things, you know? Forget about it and move on buddy! You’ve got an essay to rewrite/a purchase to figure out/a critical form to complete again, and who knows what will happen then! Will it go through? Maybe, maybe not. It will be surprising if it doesn’t! Isn’t it just so exciting?
- IshKebab 2y ago
  Damn straight. This came up in an earlier discussion about languages that rely heavily on exceptions - they sensibly don't want to expose backtraces so you get this `try: response_handler() except: print("oops!")` nonsense because the programmer literally doesn't know what went wrong and they're sure as hell not going to give you the details. I find it as infuriating as you.

smrtinsert 2y ago

Fatal Error: Operation completed successfully.

consumer451 2y ago

SharePoint is supposedly one of the keystones of Microsoft. The answer to "how can I find all SharePoint Sites where I am a member?" is: > Search SharePoint for contentclass:STS_Site How is this, and op, cluster f possible? How do these decisions get into prod?