Okay, let's remove the coercion then and have a proper libertarian solution. No one has to get vaccinated, but anyone who is not vaccinated is liable for and harm done by anyone that they infected with a disease, including joint liability for all outbreaks of that disease where the vaccinated number dropped below the number responsible for herd immunity.

By all means, go ahead and defend your right to kill people as a result of your negligence.

No idea. Open source FPGA toolchains are definitely interesting, mostly because Altera and Xilinx compete on who can produce the worst software. Having a single toolchain that could target both (which this project is still a long way away from) would be very useful. Unfortunately, high-end FPGAs vary a lot both in the core logic block structure and the number and layout of the fixed-function macroblocks that are available.

The peak power consumption is important for one other reason: heat. The machine that I was talking about is in a small NAS case (4 drive bays, slimline optical drive, power distribution board, mini-ITX motherboard, no other spare space). It also on has a (fanless) 120W PSU, so it's quite easy to go over the available power if the CPU can spike up to a high peak. I'll keep the newer Intel chips in mind when I upgrade, but it looks as if most of the mini-ITX motherboards are still limited to 16GB of RAM and being able to upgrade to 32GB would be the main thing that would prompt me to replace the motherboard. Oh, and Haswell still doesn't have working FreeBSD drivers, so that wouldn't be an option yet.

Search for 'semantic web'. XHTML 2.0 was the core of a family of standards that completely separated data, ontology maps, and presentation.

It's a radio transmitter feeding a closed waveguide. One has to ask: why haven't we seen evidence of radio transmission providing thrust before, when it's been feeding an open waveguide?

Extreme claims require extreme evidence. People who have made extreme claims before without much evidence at all are rightly categorized with the boy who cried wolf.

Ultra mobile? I don't think I've ever seen it in that configuration. It's in the same space as Intel's Atom, but unlike the Atom, AMD doesn't try to artificially segment the market too much so you can actually buy one with enough SATA slots for a NAS.

LinkedIn was ever relevant? I've had a lot of spam from them (even though I never joined or gave them permission to contact me), but I'd never consider using them to find people to hire (or to find work, back when I was looking).

Define 'proper'. Re-randomisation after every fork()? Good luck with that. PLTs at random offsets? Sure, if you're willing to pay the overhead of not being able to share any position-independent code between processes.

Depends on the AMD chip. I have a box that serves as a NAS and HTPC with an AMD Fusion E-350, which is one of their lower-power chips. Maximum power consumption is 18W for the CPU and GPU. The GPU works fine for decoding HD video (on FreeBSD, presumably it's as good on Linux). It's now around 4-5 years old and the only reason that I'm considering replacing it is that the motherboard can only handle 8GB of RAM, which isn't enough for ZFS deduplication with a 12TB pool.

True, although most password managers can generate random passwords (of varying strengths, as a recent Oakland paper showed). Using this functionality is generally easier than thinking up a password.

JavaScript can also intercept the contents of the clipboard. If you're blocking password managers, then people are going to do one of two things. Either they'll pick a (weak) easy-to-remember password, or they'll use a password manager and paste the password in. If they opt for the latter, then any malicious ad on the page can grab the password while it's in the clipboard...

I think that you're slightly missing the grandparent's point. About 10-15 years ago, there were two groups pushing new directions for the web. One group, led mostly by the W3C (though backed by Apple and a few other big companies) wanted to completely separate content and presentation. You'd have a service that would provide structured XML and then a web page or a native app that would process it and present it to the user. This would make it easy to write programs that aggregated data from multiple sources (e.g. find bus, train and flight times and prices so that you can find out the cheapest or most convenient route from A to B, including getting to and from different airports).

The other faction, led by Google, wanted to completely destroy this separation and make web pages into rich web apps that would ensure that you could only view the content in exactly the form that the authors intended. The main goal of this was to make it hard to distinguish content from ads and therefore make it hard to automatically remove ads.

Unfortunately, the second group mostly won. The grandparent seems to want people to go back to the other approach and present machine-readable data feeds so that we can then have rich client-side apps that are agnostic to the source, but present the data as the user wants. I'd like that too.

The only problem is that you may forget to turn off blocking of whatever analytics spyware they're running, so they won't get feedback that you only stayed on the page for a few seconds before leaving the site.

Read this paper if you want to know how easy it is.