Linux should stop merging file systems used by three individuals at most.
There are so many totally useless file systems inside the main tree, and I honestly fail to see why those should bloat the main tree while the junk could happily live in the hard drive of the three perspective users.
For God's sake, even POHMELFS was merged! Where does it end? Where the boundary to say NO, and keep this irrelevant code out of the tree?

Intel trying to cut down power, and ARM trying to enter the multicore, superscalar field. So far, ARM is way ahead in the smartphone/mobile market. In there, battery life is king, and Intel lags behind.

Yes, yes, Bing has been a BIG success man! Come on, and join the MS funboys party, they serve the coolaid at the entrance!
And this Morro thing, is going to be even bigger than Bing. Based on a technology that has already been rejected by the market, the success will be certain.
I can just picture the meeting:

A: What do we do with this noOneCare? Nobody is buying it, and it costs us money. We fire everyone?
B: Why is it?
A: The technology suck, and people stopped buying into the Mafia Approach (sell fear and protection) long time ago.
B: Let's try to give it for free for one year, then we fire everyone.

If you would have asked me, in 1996 or so, that MS would have become so uncool that no new software they try to push would fail, and that they'll be actually forced to give stuff for free, I certainly wouldn't have believed you.
Oh well, here we are ...

Drug companies, making disease and cure? Or is it too conspiracy theory-ish even for a boring Thursday morning?

There was a time, somewhere in the mid 90', where MS was kinda cool (granted, not search-wise). Now, everything they try to push, dissolves in flames.

Note that for the end user, it makes no sense having an "open" source, when you (or others) cannot freely install (modulo huge hacks) your mods or apps. That, and the fact that Android is a pseudo-Java-let's-do-something-different-even-though-we-have-no-technical-reason-for-it Java environment. Once you let the smoke pumped by Google and its marketing settle, and you look at it from a technical side, Android is a piss-poor implementation. I expected A WHOLE LOT more from Google, and they failed.

Choice, many times becomes really fast synonym of fragmentation and lack of standard. And this is just a bright example. The situation described is 100% conforming to reality, as far as UI kits and sound infrastructure.

LISP is a language that offload the parsing burden onto the reader. Sure is hell easier to write a LISP parser, but humans are taught since first grade to the "OPERAND1 OPERATOR OPERAND2" syntax, and LISP fscks that up. With so many languages available today, LISP is most definitely the wrong answer.

Since the advent of eventfd(), you can wait for disk AIO (via KAIO), using epoll_wait().

Lots of them, and lots of ammo!

Passing data among activities requires you to use Bundles, and the data that you drop inside Bundles must be Parcelable.

Sure, if your app is trivial enough to have a single Activity.

Which part, exactly, was faulty in his analysis? Truth is a bitch, ain't it?

Come on! Come down the tree, that I'll give you a banana.

It's wonderful! You will especially love their Parcelable interface, that you are FORCED to implement for every class (and contained/inherited class) that you plan to pass among views.
And this is not like the Java standard Serializable, that the JVM gives you for free. This is something that you are forced to implement.
Cheap poor interfaces design.