I'm not very familiar with those specific features in other dbms, but in mysql's case "on duplicate" and "replace" are two very different thing. The first is an upsert, while the other drops the old row if it exists and always make a new one.
Exactly right. And the fact that such tin-hat conversations are at all credible (reality or not) today is an indication that someone has fucked up, very badly and very existentially.
We just can't take seriously any statement made by spies, whether they're false or true. Even statements that are provably true have a good chance at being in front of a bad motive. They game others as their day job, after all.
Regarding your last point Gmail reminds me of train/plane/... events through Google now. It does also create Calendar events. My Keep remainders also pop on Google now, although they seem lower priority (?).
> I actually don't believe in that principle. If there is a spec that everyone agrees upon, violations should be accurately and loudly diagnosed and rejected.
Both preparation of the data format and processing of that data format should be conservative. Being liberal in what is accepted has unintended negative consequences.
I agree on principle. But when Marie in accounting opens the CSV that Bob from customer X sent her, if software A opens it and software B screams "error!!!", she's going to use the one that "works". And that means B's vendor will make their tool liberal of what they accept too.
Similarly for websites, that's why browsers fixes what they see rather than not showing what you are asking it to show.
Does it lead to a worse state of things for clear format, with more errors in the wild and no actual reference to base yourself on ? Yes. But it is still what end users want.
> Initially Napster lost the case in the District Court but then appealed to the U.S. Court of Appeals for the Ninth Circuit. Although it was clear that Napster could potentially have commercially significant non-infringing uses, the Ninth Circuit upheld the District Court's decision. Immediately after, the District Court commanded Napster to keep track of the activities of its network and to restrict access to infringing material when informed of that material's location. Napster wasn't able to comply and thus had to close down its service in July 2001
And http://en.wikipedia.org/wiki/Kazaa (not quoting a particular paragraph in this one as the "lawsuit" section is very long covering several countries, but it basically turns to "kazaa lost, started settling with all plaintiffs and agreed to turn into yet another legal music selling service clone").
Napster filed for bankruptcy in 2001 and blamed their "enormous legal fees" as the primary cause. (Outside of, you know, having any actual revenue.) Kazaa was in the same boat.
It's true, they did participate in some lawsuits, but they were going to be overwhelmed by the sheer volume of legal activity (the very purpose of which was to drain them of resources.) Appeals, filings in multiple districts, etc.
Back to Google/Youtube -- Google had the resources to sustain any sort of legal onslaught by the RIAA. In fact, more so as those companies started to see their profits decline steadily during the mid 2000s, and the prospect of winning a protracted legal battle wasn't so certain. As a bully, it's much easier to take the little kids' lunch money, but not so much fun when you encounter a much bigger kid on the playground.
> Personally, I don't find typing on a flat surface to be a very pleasant experience. As a touch typist, I depend on a certain amount of feedback to my fingers to identify when a key has been actuated, and I'm not always looking at my screen when I'm typing something out. With this device, how could I know the spacebar registered properly, and didn't accidentally send my cursor into another location due to an errant swipe of my thumb as it rests on the spacebar?
Well, you kind of answered yourself there
> Like [...] every tablet/phone in existance ?
Haptic feedback solve that particular issue. From what I understand some haptic technology like the one planned to use on steam console's controller also handle the "I need to feel where the keys are without looking", although I personally never experienced any of it first hand.
I agree with you that I still prefer an actual keyboard and space key on a laptop though
It really doesn't. I could type faster on a Blackberry keyboard than I can write by hand, or type on an Android or iOS device even with text prediction on the latter.
Ironically, as they started to lose market share in ~2009, Blackberry tried to pioneer the use of haptic feedback on flat-screen phone keyboards, using a vibration to simulate "clicking" the screen. It was a disaster.
I use flat keyboards on my phone and tablet out of necessity - for phones, there's really no alternative these days. But the typing experience on even the best phone/tablet is light years behind the experience of typing on a physical keyboard.
 This is different from the way that Android and iOS devices vibrate when you press a key
 Not to be confused with the earlier model which actually had you "click" the screen.
I agree, but then I genuinely believe you are mistaken in what makes you faster: it's not the feedback that the touch is pressed (what you described in the above post, and what haptic feedback currently solves), it's the feedback that the touch is even there ! In other words, it's not the pressing, but the finding/reaching the next key.
Again, I agree that current phone keyboard are faaar beyond an actual keyboard in speed, only arguing on the cause.
As I hinted in my previous message there are new haptic techs that aims to actually give a sensation of where the various keys are, I have never tried it but I hope they can do even half of what they claim.
> I agree, but then I genuinely believe you are mistaken in what makes you faster: it's not the feedback that the touch is pressed (what you described in the above post, and what haptic feedback currently solves), it's the feedback that the touch is even there
That's my point. Haptic feedback doesn't solve this, as evidenced by the keyboards that have haptic feedback on keypress but no tactile indication that the key has been located.