4k RTs and 10k likes
My next best tweet wasn't even close to this.
Hey @Google can I get into the Google Duplex beta now?
pic.twitter.com/590iPetcvs
আপনি আপনার টুইটগুলিতে ওয়েব থেকে এবং তৃতীয়-পক্ষ অ্যাপ্লিকেশনগুলির মাধ্যমে অবস্থান তথ্য যেমন শহর বা সুনির্দিষ্ট অবস্থান যোগ করতে পারবেন। আপনার কাছে আপনার টুইটের অবস্থান ইতিহাস মোছার বিকল্প থাকবে। আরও জানুন
4k RTs and 10k likes
My next best tweet wasn't even close to this.
Hey @Google can I get into the Google Duplex beta now?
pic.twitter.com/590iPetcvs
What’s noteworthy is that this is likely, and will mean that we’ve replaced high-speed, low-error computer protocols with a low-speed, high-error protocol. It’s a REST call round-tripped through a voice system. 1/
Followed by some technique to let computers know they’re talking to another computer so they can switch to a more reliable mode (9600 baud modem). And a new common question on SO: How can my services identify each other without humans detecting? I wish any of this were a joke.
Lol I mean we already have OpenTable for this. I still see value in Duplex for those services where calling a human is still necessary.
Yeah, but it should still introduce itself as a computer agent. Then it’s useful without being deceptive. M
Should human assistants be made to identify themselves as human when calling a business as well?
Absolutely, if a human is pretending to be a computer, then they should identify themselves as a human for the same reasons. If they're not pretending to be a computer, then no. If I'm a human assistant, I shouldn't mimic my employer's voice and pretend to be them either.
But is this assistant mimicking the voice of the user and pretending to be them? Would it lie if it’s asked if it’s a human? As long as the assistant is acting ethically, and working correctly, is preemptive declaration of its origin really necessary?
“Acting ethically” is begging the question. Intentionally deceiving the other party about who you are (inventing tech for the express purpose of that deception) already is ethically questionable. Much better to begin this tech with honesty rather than ask forgiveness later.
ok, I will see Lisa at [object Object]
"Undefined is not a function"
“We have available Optional(2) seats on the balcony, would you like to take them?”
The party was for 3. Array Index out of Bounds Exception.
Nice throw! I’ll catch it. Heh heh.
Null pointers? Yes. Unexpected Optional values being None? Still happens.
Yes, but you are forced to check them and when you've checked them, the compiler guarantees that there is a value, so you'll never have to check them again. This means that you only need to check for these errors at the edges of your system and can keep the internals simple.
And no, null pointers are literally impossible to get in Safe Rust, which is what you have by default when you don't activate FootgunMode.
Null pointers are not the only way to crash though. I'm not arguing that Rust is not massively safer than C. But I've been writing Swift for 4 years and crashes because of missing values still can happen.
Or, I don't know much about Swift. What do you mean by "missing values"? Is it like None :: Option a in Rust?
Yes. And sometimes we "force unwrap" the values out of those because we think we know it would never be none at that point.
Most of the time this can be avoided. In general, having to do that signifies a lack of expressiveness in the type system (or possibly a design flaw in your program). Whenever you know that something can't happen you should try to make sure that the compiler knows that as well.
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।