It is calculated according to the speed of sound at the altitude you’re in, and measured using a difference of pressure in the pitot tube.

Yeah, but Teams in Office? Is that really the main problem?

And it’s dirt cheap

Before the war in Ukraine I had stable 1 Gbit/s for 5$/month with two dedicated IPs

Here in Ireland you get 100 Kbits/s sometimes because they can’t pull you a fiber connection and 4G towers are overloaded to hell, and it costs 20-40€/month

I’m pretty sure it’s either a myth (that it doesn’t work) or some US-centric thing, because when I worked as a delivery guy, I used to go through probably hundreds of different elevators in high-density residential buildings, and most of them have doors that stay open very long to allow baby strollers and heavy appliances to be placed inside, and on pretty much all of these the door closing button works, immediately closing the door

This is what I and many other programmers have done (not the removal, but fake delays), because it improves user experience, actually:

1.When the user clicks a button that should take long in their mind (like uncompressing a zip file etc) but is actually fast, it might seem like something is wrong and it didn’t work

2.When the user transitions between layouts of the application, if it loads everything too fast it will look too abrupt, a fake delay will be made here if a transition animation is not possible/doesn’t fit

Gaskets brother, waterproof phones existed for a long time, they have been there since phones had SIM cards under their batteries

Look at things like mechanical watches where a watch that is rated for less than 100 meters of depth in dry test chamber is called “delicate” even though you can unskrew both the crown and the back with your hands on pretty much all of them

It’s called amd64 because AMD invented the x86-64 processor instruction set, it works both on Intel and AMD