The TFA mentioned that it only supports a tiny subset of the functionality that OpenSSL supports. I'm reasonably certain that they didn't include the old and broken stuff in their rewrite.

Maybe you can talk securely. Nobody has publicly announced any vulnerabilities in HMAC-MD5 yet, but that MD5 piece hanging off of there makes me nervous. If Amazon is willing to say that they no longer support Windows 3.11 for Workgroups users buying products from the Amazon store, it is their call. They have to weigh the loss of customers over discovering later that some weird long forgotten part of their OpenSSL implementation gave the keys to the kingdom over to the hackers.

No, but you will need the CS degree to be a good programmer. If you know what is going on under the hood you can avoid those O(N^5) operations that make your code inefficient. If you just blindly use whatever looks vaguely correct in the standard library you'll never know why your code is so slow.

Only if there is some other device on the network that needs data 24/7. For most people the router is going to go mostly idle once the laptop is closed because there's nothing for it to be talking to. The only thing it should be transmitting is the occasional beacon.

The description makes it sound like they just cut the Tx power on the router by two thirds when you enable the mode, which means it will just have a much shorter range. Even better: This would only help if the woman stayed near the router, she's going to get a lot more "radiation" from her laptop, since it has a similar radio and of course is much closer to her. Even if the science were sound, this wouldn't work. It's both dumb and pointless.

You don't need to buy this card if you're happy gaming at console resolutions. Even 6 year old midrange cards can push modern games just fine if you're willing to accept 720p at 30hz. You can even hook up the controller to your PC if you hate the easy precision of a mouse.

The problem with orbital mining is that it depends on the presence of orbital manufacturing. And orbital manufacturing depends on the existence of raw material. There is a chicken and egg problem unless you're willing to try to safely deorbit many tons of material every year, which is a terrifying prospect. It doesn't really make sense until we're building some sort of enormous space station or space ship in orbit and the launch costs exceed the eye popping costs of starting up an orbital mining/refining/manufacturing industry.

While technically true, in practice everybody does the 64/64 split, especially once you get out onto the Internet. Sure you can do whatever you like on your local network, but don't expect it to go beyond your border router.

True, unless you intend to connect your local network to the Internet, which I think most people are planning to do. You also don't need a global IPv4 address unless you want to connect to the Internet.

Anybody who moves between networks, like a cell phone? You still do route aggregation in IPv6, so even if your host ID (lower 64 bits of the address) don't change, the network ID (upper 64 bits) will when you move between networks. Otherwise you would need to propagate every single device in the world into the global routing table, and that doesn't scale.

Kind of true. Router autodiscovery works, but has some problems. It doesn't provide DNS information to the clients, nor does it allow the clients to populate their hostnames in the local DNS the way a DHCP server does. This makes it far from ideal when you want to allow for client to client communications. It also lacks any sort of authentication mechanism which makes it vulnerable to spoofing attacks. Router autodiscovery is a really incomplete solution.

Nuclear isn't particularly "clean"--refining the fuel is messy, but it is low carbon.

It kind of is, but they put in so much information that I can't hold it against them. Look how many code fragments with common errors there are in there. This is a quality article.

And then one of the stupid old PLCs craps out and you discover that they have not been made for 20 years and all of the old stock is exhausted... Now you have a crisis where you have to rebuild a major part of your system at great expense.

IIRC they did remove some of the more obscure APIs, but honestly most of those were research projects that were never used in real life, so they shouldn't break anything. The OpenBSD guys compile their own ports tree against LibreSSL and have only had a small handful of applications break I think.