You are glossing over the fact that Microsoft still plays hardball over Windows license price and associated kickbacks with each individual OEM.

The oems can fight back, but are they? All of them? If the answer is no, even for some of them, there are still Sherman act violations. FYI, the touchstone test for Sherman act: "is market power being exercised?"

Only if the DoJ continues to look the other way in the face of continuing flagrant Sherman act violations in the form of secret exclusionary agreements with OEMS and the like. Microsoft never made it on merit...

Speaking of which, it's about time for another massive fine from the Eurocrat direction, wouldn't you say?

I too am typing on a PC, but it is not running Windows.

Of course Windows is still relevent, it remains the authoritative source of Windows reboot sounds.

You have a kid? Your phones are used for gaming. You never ever play a game yourself? You're the only one. I suppose you never email or browse with them either :)

Java is famously crappy and sluggish for GUIs too, and barely tolerable for web. As a rule of thumb, whatever you are running on your server will run about 20-30% faster if you recode it from Java to C++. First hand experience speaking here, and you will find multiple confirmations out there. Java is just a pig, with its jitting, memory hogging, heavyweight thread locks, etc, etc.

Mind you, Java performs better than Python or Ruby so at least there is that. But never labour under the illusion that Java can compete with C++ or C in terms of throughput, latency or memory footprint. You code in Java so you can use cheaper programmers, that's it. Otherwise, if you can afford it, you do the job properly in C++.

That is wildly wrong. One billion Android handsets running OpenGL ES make you are about as wrong as it gets.

Microsoft has basically run out of solutions. Their best strategy now is to sink as slowly as possible.

No they aren't, when did you last check?

What is intuitive about 1/2 == 0?

Not only that, but even when it does work it tends to break on dist-upgrade (or yum equivalent). Needs fiddling. Life is too short for that, that's the kind of crap I binned Windows for. Plus, the binary block tends to do things its own way whether or not that plays nicely with other components, not being subject to peer review and all.

Your report just screams "I'm running an ancient kernel and distribution with an early, dodgy compositor." Try upgrading to current and report your results. To prove you're not a troll, post a bit of the oops message if you get a crash on an up to date system.

Because the driver is binary and the card specs are closed?

troll