One example among the many things the court found they did was to tell OEMs that they wouldn't license Windows to them if they _also_ included Netscape preinstalled in their computers.

The stated purpose, from internal emails, was to prevent Java from becoming the de-facto API for writing applications, which at the time was win32. This was a gigantic barrier of entry that protected Windows' monopoly and they did all those shady things to keep it raised.

Your theory cannot explain how Bing associated that "next site" with the specific search term the user had entered in Google.

If you had clicked a link on HackerNews, it wouldn't have shown up in Bing under some random search phrase. It's obvious that Microsoft parsed the search query out of the google.com URL, and the only reason why you'd do that is to mine what results were being presented for each search query.

Google did containers in Borg many years ago, and many of its servers are written in Java.

lol specifically, what Google search results Bing Toolbar users click on and what query they had entered in Google to get those results.

> But in order to arbitrage this, you have to be willing to pay women and men differently.

A very simple way to arbitrage it without discriminating is to set your wages somewhere between what others pay men and women. Women will flock to you, as you pay better than elsewhere, while men will tend to leave to the discriminating jobs. You pay everyone the same, but the result is your cost in wages is lower than your competitors'.

When home VCRs became commonplace, creating an automatic copy of a broadcast was still illegal. Some German high court ruled that people's right to privacy in their own homes trumped law enforcement's interest in enforcing copyright, so the law was unenforceable in those cases. Hence was born the exemption for "copies for private use", and the related "tax" applied to sales of VCRs (and later on, blank CDs and DVDs) that was used to pay off author associations.

One of the two examples he cited in his introduction, the Android one, wasn't even caused by an unhandled OOM error. Android by design will kill unused processes if they're occupying memory that the foreground process needs.

If we want software without bugs, removing hidden allocations in languages is far down in the priority list.