Because it wasn't tested well enough? For example, in the case of the system call entry path, Andy Lutomirski found a bunch of bugs over the past few months - including CVE-2014-4508, CVE-2014-9090 and CVE-2015-2830. His changes for 4.1 include the addition of regression tests as well as cleaning up that code.

Yet all the browsers consider unencrypted connections more secure than connections encrypted with a self signed certificate.

No. They consider that entering or following a link to an 'https:' URL means that you expect a secure connection. In this context, a self-signed certificate that has not been whitelisted is an error.

MPEG set up the MPEG-LA that serves as a patent pool

No, they did not. There are a lot of the same players there, of course, but they have no formal relationship.

This is good news; I'm glad to see at least one misogynist leaving Wikipedia.

Sadly, it still seems to be run by a bunch of young white guys fighting for the importance of hosting porn and claiming the consensus of their privileged group is "neutral". ArbCom has censured admins for fighting back against lies spread by GamerGate, with a ban that may apparently prevent them fixing any abusive edits to articles about women.

99% of the resumes that HR sent me

Maybe part of the problem is letting HR filter them first. If they don't know how to spot bullshit then they may effectively favour the liars.

As described, It is full duplex - both sides transmit simultaneously and have to cancel their own signal and its echoes from the combined received signal. Twisted-pair Ethernet already works this way, but in the radio medium the echoes must be even more challenging to model and cancel.

USB host controllers generally support DMA, but the drivers on the host do all the buffer management so the device cannot choose which addresses to read and write. Of course, it can take advantage of driver bugs such as the HID descriptor parsing bugs that were fixed in Linux a few years ago.

This is why I claim it's spyware. Sure, you can turn most of those things off, but the intent of turning them on by default is to capture that information from most users.

you know what I don't use every day? Debian, Do you know why? People like you. I've been using Linux for 20 years and it's people like you that get in the way of progress.

I'm not getting in the way of anything. The kernel is team-maintained and I've explained how this change can be made without my help.

Linux 3.19 is already packaged in experimental and I expect to end up maintaining a linux package in jessie-backports, so that will be another option for people who really want to use Chrome/Chromium.

I do dislike Chrome and I'm not going to pretend otherwise. Aside from its being spyware (in its default configuration), the Chrome/Chromium developers have previously added requirements that make Chromium unsupportable in Debian 7. We could add this kernel feature now, but I strongly doubt that will be sufficient to keep Chrome/Chromium running on Debian 8 until its EOL.

Please note that I am not NAKing the change, but I'm also not going to be the one to make it happen.

Path Intelligence (reference)

"When it breaks, you're fucked", just like anything you run as pid 1. Except you can still use the init= command line parameters to run something different (or possibly break= to stop in the initramfs).

"Obsoletes 20-30 years ... of how to use linux tools". Huh, I must have my Linux history wrong as I could have sworn it was started in 1991.

"No real new features" because all its new features, are somehow not real according to some AC?

"Virtually untested" except by every major distribution?

Insightful, my arse.

or have a problem with it randomly flipping to headphones on loud parts on another machine

Because obviously broken jack detection is the fault of the daemon, not the hardware or sound driver.

In many hard drives the flash only has the first stage of the firmware, while the rest is on the disk - and there's lots of spare space there.

Thunderbird tends to reformat mails after signing by Enigmail, invalidating the signature. Enigmail has some workarounds for this, but nothing perfect. The two projects should have worked together to hook Enigmail in at the right step, but somehow it's never happened.