Back in the day, phone calls outside your area code were priced by the minute. Rates varied depending on distance, time of day, and where you dialed the number yourself. (Yes, you might have literally "dialed", using the rotary dialing mechanism.) If you didn't dial it yourself, you dialed "0" and asked the operator do you it for you. Why would you do that? Well, you know, those phones were complicated things.
Dated September 13 1977
A direct-dialed call from Ithaca to Washington DC, during the day, would cost you $20/hour, equivalent to over $100 today.
That's why some old people still get overexcited when they receive a call from a distant location.
1995?
CBORD is mainly a software company, but in those days, it was common to replace cards in PCs in order to add memory or make other mods. This was the tool.
If you recognize the company, give a shout.
Ooops, sorry, the book is about Feynman, but was written by Ralph Leighton.
The book chronicles Feynman and Leighton's decade-long effort to visit Tuva, a journey that was both physical and bureaucratic. During the Cold War, travel to Tuva, located within the Soviet Union, was incredibly difficult. They faced numerous obstacles, including stringent visa requirements and communication barriers
The recording was bound with the book. It contains a few minutes of Tuvan throat singing performance.
Back in the day, phone calls outside your area code were priced by the minute. Rates varied depending on distance, time of day, and where you dialed the number yourself. (Yes, you might have literally "dialed", using the rotary dialing mechanism.) If you didn't dial it yourself, you dialed "0" and asked the operator do you it for you. Why would you do that? Well, you know, those phones were complicated things.
Dated September 13 1977
A direct-dialed call from Ithaca to Washington DC, during the day, would cost you $20/hour, equivalent to over $100 today.
That's why some old people still get overexcited when they receive a call from a distant location.
I got here first.
Here’s a more complete lyric , for context
Oh, thunder only happens when it's raining Players only love you when they're playing Say, women, they will come and they will go When the rain washes you clean, you'll know You'll know
I’d translate to a meaning of : some things are situational and temporary, and you should be careful to assume that they will last. Especially good things. There’s also a sense of being taken advantage of.
It's hard to hold a train of... could we get a trainload of this? That would be awesome. Some awe, anyway. Awemuch? Yeah, it would be awemuch. Buy now.
contains mercury. You don't find this, anymore. I have PTSD (jk) from the sting of the alcohol in a wound, and the orange branding that it left behind.
Somebody sent me an Expedia invitation to view a property. Clicking it on iPhone produced the screen shown.
"Clicking below will copy this page".
uh, what does it mean to copy a page? This page? Why would I want to copy this stupid page?
"You'll be redirected to this pages in the app"
Grammatical error.
"Get the app/Get the app without copying. "
Where's the option to open it in the phone's browser? I don't want to install an app just to look at a property that somebody invited me to see.
I think that by "copy this page", they mean that when the app opens, you'll be positioned on the page identified by the original link that I clicked. Why offer that option? If somebody sent me a link to a specific property, the intention is clear.
They've taken a perfectly simple operation and made it perfectly obtuse.
So bad.
The average person would probably figure this out. Especially given the context, where they just entered the PIN. It's just aesthetically displeasing, and evidence that nobody thought about the user point of view. They didn't even notice the redundancy of "PIN Number". And what's a "field", to a non-coder? Why didn't they just say "Invalid PIN"?
Imagine if you were trying to login to an application but entered the wrong password, and the message said "OAuth was unable to authenticate due to invalid credentials". It works, but it's as ugly as a pimple on the Mona Lisa.
If your application does not handle concurrent requests or do other work that requires multiple threads, and you use await on every async call, then you will see little or no benefit from the async model.
But if your application does handle concurrent requests, the situation is very different. You get benefit, even if you code await on every call.
When an async method ultimately does I/O, the thread of that that context is freed to do something else. The "else" can either be more work in that execution context (if you didn't await), or, the thread can be allocated to service another request. Re-allocating an existing thread to work on a different request is much more efficient that allocating a new thread to that other request.
Not just the "PIN Number" part. Though that's bad enough.
"Invalid data?"
"In a field?"
Some coders really shouldn't be allowed to touch the UI.
Not just the "PIN Number" part. Though that's bad enough.
"Invalid data?"
"In a field"?
Did anybody THINK about this?
Salt does not leave water that is sitting out. In fact, some water evaporates, leaving the salt behind, so the result is water that has a higher concentration of salt
Is softened water bad for plant?
houseplants