Windows NT used a STREAMS-based networking stack, culled from some other UNIX (not directly, but using the concepts and frameworks), not a BSD-derived networking stack.

I have no idea how the DOS-based Windows networking stack developed. But it wasn't pulled from any BSD.

A few command-line utilities (ftp.exe is the most common cited one) were pulled from BSD sources, though.

Except when you start talking about netmap. :) That's a userspace network stack that can push millions of pps, on sub-GHz systems.

There's even a netmap-enabled version of the IPFW packet filter that runs in userspace, filtering millions of pps on sub-GHz systems.

And there's an applications ecosystem starting to grow around netmap that keeps all network-related packet processing in userspace.

As a twist, netmap and IPFW are also available on Linux, and provide better performance than the in-kernel network stack and iptables. :)

Google searches for "netmap" and "FreeBSD" will give you lots of information on pushing millions of pps through 900 MHz single-core machines. Netmap is also available on Linux. There's even a netmap-enabled version of IPFW that allows you to do packet filtering and routing completely in userspace, again will millions of pps. IPFW is also available on Linux, although I don't know if the netmap-enabled version is.

Google searches for "openconnect" and "FreeBSD" will give you lots of information and blog posts from the Netflix guys about why they picked FreeBSD, and how it all works, including details on the networking.

Google searches for "Adrian Chadd", or "RSS scaling", or similar terms will show you threads and posts on various FreeBSD mailing lists with information detailing a lot of the MSS/RSS work that's going into FreeBSD 11, and several projects that build off that. Those also have links to other information around sockets and similar.

Google searches for "NUMA" and "FreeBSD" will bring up mailing list threads that cover the different projects being undertaken to improve the CPU affinity and thread locality and all that jazz.

Sure, it would be nice if the OP had posted links to the info, but it's not like the information is secret or hard to find.

What makes this thing truly "Raspberry Pi-compatible" is that it uses the same Broadcom SoC. There's nothing Samsung about this thing.

AdBlock+ is available for Chrome as well. Why not use the same product everywhere?

They're talking about the Score, not the compression algorithm. And your link doesn't mention anything about the Score.

Maybe they're all at Starbucks (which, by the way, editors, has no apostrophe).

Actually, in the context of the headline, it *does* have an apostrophe, just not where they put it: Starbucks'

After all, the wireless charging mats belong to Starbucks.

There are already e-libraries out there that just have computer stations and ebook download terminals. And I believe Apple? was trying to build a couple more.

Not to mention all the time spent waiting for the 17 different CDN services to respond to download content, all the time spent waiting for the 23 different ad networks to respond to download content, all the time spent waiting for the various DNS servers to respond with the correct IPs, etc.

Sure, the actual downloads of the various bits of data is very fast. But that's the shortest/quickest part of loading a web page. And all the other bits and bobs and bottlenecks are the same, regardless of what speed of network connection you have.

Yes, exactly.

They need to stop with the hybrid crap where there are two drivetrains, and the pure-electric crap with horrible range and non-existent charging networks.

The ultimate EV is one with a gas/diesel generator that does nothing but charge the batteries to provide virtually unlimited range using the existing gas station network.

Stick a battery pack that can handle ~150 Km (~100 miles) into the EV. That covers just about everyone's daily city driving.

Then install a small gas or diesel generator into the car. All that generator does is charge the battery. It doesn't power the wheels, it doesn't drive the car, it doesn't to anything except provide electrical power to the car.

That way, you have the means to use the EV for long trips. Need more than ~150 Km range? Fill up the little gas tank and carry on as per normal.

The GM Volt is so close to being the perfect EV. All they have to do is remove the non-electric drivetrain, disengage the gas motor from the wheels, and tune the gas motor to run as a generator, and that's it.

Except that after years of polite "you need to fix this" requests and no follow-up from Kay ... what do you consider the appropriate response? This isn't the first time Linus has called him out. But it's the final time; the time that broke the proverbial camel's back.

Kay's been a kernel developer for years, and has clashed with Linux many times in the past, all for the same reasons: Kay patches something, breaks a lot of things, says everyone else has to fix their code to work around the things he broke as it's "not his problem". Linux has finally had enough of that attitude.

Those are all issues with the cable and Lightning protocols, not the actual, physical connector.

The problem with MicroUSB and even full-sized USB is that stupid tongue in the middle of the socket that goes inside the plug on the cable. That tongue can be easily broken by moving the device with the cable plugged in. I've snapped that off a phone and a desktop now. And there's no way to fix it without replacing the entire socket ... not easy when it's soldered to the motherboard.

The Lightning socket/plug is going in the right direction. The contacts should be on the outside of the plug on the cable, and along the inside walls of the socket. The plug should be solid (no holes), and the socket should be just a hole (no pins, tongues, or whatnot).

Compare the headphone jack/socket. Connectors around the inner wall of the socket and on the outside of the plug. Plug is solid. Socket is a hole. Impossible to plug it in wrong. Take design cues from that, from the Lightning connector, hell even the old mini Christmast lights got it right.

Pins and tongues inside of sockets that a plug has to go around is just dumb. Didn't we have enough issues with bent pins on VGA/Serial/Parallel/PS2 ports to realise that was the wrong way to do things?

Except when the OEM puts the USB slot in upside down. Like the Nexus 7. Or the front USB slots on a lot of desktops.