https://www.currentaffairs.org/2018/07/how-horrific-things-c...

https://historynewsnetwork.org/article/10903

> Throughout World War II, the American media published and broadcast timely, detailed, and accurate accounts of what was happening to the Jews in Europe. The New York Times alone printed nearly 1,200 articles about what we have now come to call the Holocaust, about one every other day.

> The articles in the Times and elsewhere described the propagation of anti-Semitic laws in German allied countries; death from disease and starvation of hundreds of thousands in ghettos and labor camps; mass executions in Nazi-occupied Russia; and mass gassings in Auschwitz, Treblinka, and Maidanek. The articles also indicated that these were not isolated incidents, but part of a systematic campaign to kill all the Jews in Europe.

> And yet, at the end of the war and for decades afterward, Americans claimed they did not know about the Holocaust as it was happening. How was it possible for so much information to be available in the mass media and yet simultaneously for the public to be ignorant?

> The reason is that the American media in general and the New York Times in particular never treated the Holocaust as an important news story. From the start of the war in Europe to its end nearly six years later, the story of the Holocaust made the Times front page only 26 times out of 24,000 front-page stories, and most of those stories referred to the victims as “refugees” or “persecuted minorities.” In only six of those stories were Jews identified on page one as the primary victims.

Google's market problems aren't app developers responsibility to overcome just because they are 'sort of known'.

I think you missed this line. Presumably they were doing quite well for themselves, got nailed by some change Google made, and now are not recouping any costs due to all the lost sales.

Sadly, bryanlarsen is correct about Google's culture, especially when it comes to the code they've written: the search code is doing what we told it to and there won't be any reconsideration of decisions made about code.

However, I rather disagree that Amazon will ever provide a panacea. The Amazon market currently poses its own problems to app sellers. Once your app is on their market, you do not control it. Amazon sets the price, Amazon sets the description and classification. If Amazon hires some marketing copy-writer to write your app's description and that person doesn't know anything about your app, guess who gets to deal with angry customers who didn't get what they were expecting? It won't be Amazon.

Amazon has had some technical hangups that be explained by 'early product bugs'. While I expect such problems to be eventually ironed out by better QA and development processes, my understanding is that they have not yet been ironed out.

Finally, the Amazon market is tiny compared to Google's. If I told you that putting your software on Amazon's market would net you 5% of the sales you get on Google's, but you'd spend just as much time fighting through problems in the market itself, would you jump on that opportunity? I probably would not.

I've asked two questions (C#/.NET so there's a large pool of potential answerers) and neither question ever got the answer it deserved, even though both got answers from genuine experts (Jon Skeet and Eric Lippert). I found the answer to my first question on some MSDN blog after I asked on StackOverflow, the second question is still unresolved.

There's no place that's documented except for the developer forums.

All I wanted to do was add a `Like` button that would broadcast to the clicker's friends timeline. What could be simpler? Just copy and paste their code onto your page and you're done. Right?

The second sentence on their documentation page says "when the user clicks the Like button on your site, a story appears in the user's friends' News Feed with a link back to your website."

But it turns out that's not true. It turns out you have to jump through all kinds of hoops to get that behavior. The documentation for their simplest and most used integration feature couldn't go one paragraph without falsehood.