You didn't read to the end of my post, did you?

Don't claim copyright on every video, this will make you guilty of perjury under the DMCA. Claim copyright on one video and then claim that every other video appears to be a derived work of that video. This is exactly the mechanism that the big studios use.

The perjury clause doesn't say what you think it says. If I own the rights on work A, to file a notice on work B, I claim that work B infringes work A. The perjury clause kicks in only if I do not own the rights to work A (or represent the person who does). If work B doesn't infringe, then that's a matter for the courts. This is quite annoying, but it does make sense. It's clear cut if works A and B are the same, but not in the case that B is a derived work of A. A court has to decide whether the use of A in B counts under fair use or not.

The counterbalance for this is that the DMCA does indemnify YouTube if they respond to a counternotice and reinstate the work. If you, the owner of work B, think it does not infringe then you send such a notice to YouTube. I then have no further recourse against YouTube and must take you to court directly.

The problem here is that it's very easy to automate sending takedown notices, but very hard to automate sending counter-notices. Mass-sending of automated takedown notices was something that the authors of the DMCA didn't foresee and the act probably needs amending to require the notice to explicitly state (under penalty of perjury) the person who has compared the works and their reason for believing that they are infringing.

In the UK, university research departments are assessed base on the Research Excellence Framework (REF, formerly the Research Assessment Exercise [RAE]). Each faculty member is required to submit 4 things demonstrating impact. These are typically top-tier conference or journal papers, but can also be artefacts or examples of successful technology transfer. The exercise happens every four years, so to get the top ranking you need to write one good paper a year. The only incentive for publishing in second-tier venues is meeting other people who might lead to interesting collaborations.

Reproducing work is often a good thing to set for first-year PhD students to do. If they reproduce something successfully, then they've learned about the state of the art and are in a good position to start original research. If they can't reproduce it, then they've got a paper for one of the debunking workshops that are increasingly attached to major conferences and that's their first publication done...

Didn't Apple go through this exact same issue with the iPhone app store a few years ago, and they fixed it?

Predicting that x86 would go away was more wishful thinking than anything else. At the time, Intel had just switched from pushing the i960 to pushing the i860 and would later push Itanium as x86 replacements (their first attempt at producing a CPU that it was impossible to efficiently compile code for, the iAPX432, had already died). Given that Intel was on its second attempt to kill x86 (the 432 largely predated anyone caring seriously about x86), it wasn't hard to imagine that it would go away soon...

I found Modern Operating Systems better than the Minix book. The Minix book tells you exactly how a toy OS works in detail. Kirk McKusick's Design and Implementation of the FreeBSD OS (new version due out in a month or two) tells you how a real modern OS works in detail. Modern Operating Systems gives you a high-level overview of how modern operating systems work and how they should work. If you want to learn about operating systems, I'd recommend reading the FreeBSD D&I book and Tanenbaum's Modern Operating Systems and skipping the Minix book (which was also a bit too heavy on code listings for my tastes).

Minix has been BSD licensed for well over a decade. I'm not sure exactly how long, but it was when I was an undergrad and that was a depressingly long time ago now. As the kids today say: Old troll is old.

While this is true, it's worth noting that a lot of the compartmentalisation and sandboxing ideas that most of the userland programs on OS X employ (either directly or via standard APIs) have roots in microkernel research. OS X is in the somewhat odd situation of having userspace processes that are a lot more like multiserver microkernels than its kernel...

This is confusing in Brussels, because there is Université libre de Bruxelles (Free University of Brussels), but there is also Vrije Universiteit Brussel (Free University of Brussels), a different university.

They're good at the animations and the easter eggs, but they lack things like a pause button which is really irritating if the phone or doorbell rings a little way into the video.

If you're looking at any web site that is that general, then you're in the wrong area. Job ads are like any other ads: they're useless without doing some targeting.

I thought it was a fairly faithful adaptation, but I admit I got bored some time in Season 2. The pacing in the book can be slow at times, but when transferred as-is to a visual medium it's amazingly tedious.

Seriously? You want competent people and you advertise on Craigslist and Monster.com? No wonder you think there's a skills shortage...