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

Actually, I can be adequately entertained with a ukulele, I don't strictly need a TV at all. But if I watch video, good quality video equipment pleases me, just as good quality sound equipment does. This is orthogonal to any content quality issues.

The different between 1080 and 4K is stupidly obvious on any 60" TV, and readily apparent to connoisseurs on much smaller displays in the same way that the difference between a consumer speaker and a studio monitor is obvious to any sound technician even if it may be completely missed in favor of bass boost etc by the average consumer. If you care about image quality, you care about 4K. If you think your boom box sounds pretty damn good playing Lady Gaga then you will probably be happy with 1080p for quite some time, or standard DVD for that matter.

Well, if Sony and their idiot partners had not made such an absolute hash of the Blu ray experience by excessive DRM, offensive warnings that can't be skipped and crass shovelware loading of endless previews that are opt out (and sometimes, randomly either can't be fast forwarded or can't be skipped) and super slow clumsy content menus due to the braindamaged Java tie then consumers might actually care about the next Blu Ray standard. But Sony did make a hash of it and delivered an experience that makes you want to throw a shoe at the TV every time. The kick in the face that just keeps kicking. Sorry, no more crappy optical disks rubbing my face in whatever a content provider wants to rub my face in. Solid state, hard disk or streaming for me, Blu Ray can fuck off and die, and so can Sony.

It is more than a little impressive how successful some people can be at deluding themselves into believing that efficiency does not matter, even when it does. GP is a typical example. A common manager belief: "I must be brilliant because I got promoted into this position of managing lots of devs, so every little ass fart of an idea that I hold dear must be right". In any case, an engineer who dares to disillusion/correct tends to do so at the risk of their career prospects. Or maybe they would be happier and richer getting out of that shop anyway.

That's why the chinese made a proverb for it

Easy solution: if you dont' want exceptions because you are implementing hard real time stuff, then don't use exceptions then. In c++, if you compile with exceptions disabled then there is no overhead whatsoever. You would probably also have to avoid D's standard library.

There is nothing unusual about this (and I wonder why I need to explain it to you). The Linux kernel is programmed like that: there are standard libraries defined for C, but kernel code doesn't use them, because they do things like malloc that are unacceptable in kernel.

Frog. Well.

I'm not wrong about exception overhead. I know why this is so, plus I measured it to verify. What support do you have for your bald (and nonspecific) assertion?

ACL is probalby the actual Android libraries, since they are BSD-licensed. Google might end up regretting that.

Civilization is amazing, even for shooter addicts.

It does seem more than a little idiotic to omit Android considering which way the market share wind is blowing.