If restaurants functioned like Microsoft:

Patron: Waiter!
Waiter: Hi, my name is Bill, and I'll be your Support Waiter. What seems to be the problem?
Patron: There's a fly in my soup!
Waiter: Try again, maybe the fly won't be there this time.
Patron: No, it's still there.
Waiter: Maybe it's the way you're using the soup; try eating it with a fork instead.
Patron: Even when I use the fork, the fly is still there. 
Waiter: Maybe the soup is incompatible with the bowl; what kind of bowl are you using? 
Patron: A SOUP bowl! 
Waiter: Hmmm, that should work. Maybe it's a configuration problem; how was the bowl set up? 
Patron: You brought it to me on a saucer;what has that to do with the fly in my soup?! 
Waiter: Can you remember everything you did before you noticed the fly in your soup? 
Patron: I sat down and ordered the Soup of the Day! 
Waiter: Have you considered upgrading to the latest Soup of the Day? 
Patron: You have more than one Soup of the Day each day?? 
Waiter: Yes, the Soup of the Day is changed every hour. 
Patron: Well, what is the Soup of the Day now? Waiter: The current Soup of the Day is tomato.
Patron: Fine. Bring me the tomato soup, and the check. I'm running late now.

[waiter leaves and returns with another bowl of soup and the check]

Waiter: Here you are, Sir. The soup and your check.
Patron: This is potato soup.
Waiter: Yes, the tomato soup wasn't ready yet.
Patron: Well, I'm so hungry now, I'll eat anything.
[waiter leaves.]

Patron: Waiter! There's a gnat in my soup!

The check:

Soup of the Day . . . . . . . . . . . . . . . . $5.00
Upgrade to newer Soup of the Day. . . . . . . . $2.50
Access to support . . . . . . . . . . . . . . . $1.00

It's 2018 and folks are still stuck "collaborating" on documents by sharing them back and forth over email.

MS Word Doc created in Office 2016 will not open in Office 365.

THIS IS WHY GOOGLE IS WINNING!

I've been using the Square REST API and I spent one hour thinking there was something wrong in my code until I f** found that THEY were not following OAuth 2 guidelines, which made their workflow incompatible with the OAuth lib I was using, so I had to mark an exception for Square's OAuth from the rest of my OAuths. Specifically, RFC 6749 Section 4.2.2 and 5.1.

However, after reading OAuth 2 guidelines, I became angry at THEM instead. The parameter `expires_in` should be the "lifetime in seconds" after the response. This will always be innevitably inaccurate, since we are not taking into account the latency of the response. This is, however, not a huge problem, since the shortest token lifetimes are of an hour (like f** Microsoft Active Directory, who my cron jobs have to check every ten minutes for new access tokens). Many workflows (like Microsoft, Square, and Python's oauthlib) have opted to add the `expires_at` parameter to be more precise, which marks the time in UTC. However, there's no convention about this. oauthlib and Microsoft send the time in Unix seconds, but Square does this in ISO 8601. At this point, ISO 8601 is less ambigious. Sending a raw integer seems ambiguous. For example, JavaScript interprets integer time as Unix _milliseconds_, but Python's time library interprets it as _seconds_. It's just a matter of convention, a convention that is not there yet.

Hope this all gets solved in OAuth 2.1 pleeeaasseee

What's with the updates in our technology ? has it always been this situation that Computer manufacturers stop providing upgrades after a few time?

Like android tries hard, but no device older than 3 years is going to get the latest android . i phone guys say they get the latest ios on iphone 6 plus, but isn't that also like 6 generations later device?what about iphone 4s or iphone 3g or iphone1 ?

So far i guess microsoft and laptop manufacturers are winning at this area... i believe i could find some peeps with their 10 yo fatass pc running win 10 . Or maybe iot, i am not sure but i wonder if those microwaves won't be compatible with the latest version of whatever OS they are using (if there is a mechanism to update one)

I was actually reading about the operating systems. My point regarding this post was that the OS's have been architectured to be modular and h/w independent for years . Nearly every OS has this HAL layer which literally has the function to abstract hardware and give apis to system such that whatever the hardware there is down below, the system would not have to worry.

So why does new updates to the os not pushed to older devices? why do manufacturers give the reasons that we don't push updates because the hardware is incompatible with the os?