It might be different if Bennet were a frequent poster and would be actively engaged in discussions, but he's not. He's just some guy who once heard that brevity is the soul of wit and went off to write ten thousand words explaining what it meant.

If she brings three of her friends then there are four girls, so you can have two pairs of girls and you can catch up on sleep.

The queuing theory to work out the solution gets very complicated (far more complicated than I can be bothered with for a Slashdot post). The distance between the cars is probably enough (although you'd want some margin for error) if they're all staying one breaking distance apart, but they'd also need to make sure that they are either regular, or that the streams in each direction have the same gaps. That's going to require some rearrangement on the road, which will lead to the ripple effects that the grandparent mentions. And, if there are going to be human inhabitants in the cars, then you will still need them to decelerate if they're turning, rather than just crossing.

I really enjoyed the miniseries and the first two full seasons. By then you could tell that, although the Cylons had a plan, the writers didn't. Season 3 (according to Wikipedia numbering - it says 'Season 4 on my boxed set') started okay, but the boxing episode reminded me of TKO from Babylon 5, which was the worst episode of the entire 5-year run, and it went downhill from there. The whole 'God did it' ending was almost as bad as 'they woke up and it was all a dream'. I watched most of Season 4 thinking 'the next episode is going to be better, right? The writers are just having a bad day...week...year...'

The scene with Jabba was in the novelisation that George Lucas wrote in 1977. I was under the impression that it was filmed, but didn't make it into the original because they couldn't make it look anything other than terrible with the special effects at the time.

I really enjoyed the series, but I watched it aged about 9-12. I've avoided watching it again, because I think I was probably in the right age demographic the first time. Knight Rider, on the other hand, I re-watched recently and still enjoyed.

At least this wasn't copied from someone else, as Glen A. Larson was the creator of both.

The reason that Apple disabled this is that a lot of SSDs have really buggy TRIM implementations. This observation wasn't unique to Apple: Microsoft and the Linux kernel defaulted to TRIM being off until quite recently. Apple could afford to turn it on for their own SSDs because they did extensive compatibility testing of those before shipping them.

Now, it doesn't really make sense, but enabling it automatically would likely burn some users, and bug reports about data loss lead to a lot more anger than bug reports about lower performance.

TRIM says 'I won't read back from this sector, so you can erase it whenever you want'. That makes it a bit easier for the wear levelling to work. It isn't essential though. An SSD controller can remap sectors at will. Typically, it will keep track of the age (number of erase cycles) of each cell and the time of the last erase. Once a cell reaches a certain age it will write some old (and therefore hopefully infrequently changing) data onto it. Current SSDs, because of the low reliability of individual flash cells, over provision by quite a lot, so it's relatively easy to structure the writes so that everything is a copy. This doesn't even affect performance, as the reads and writes can happen in parallel. The only thing that hurts performance is if you need to block a write waiting for an erase to finish.

Although the mean population density when you average across land mass is pretty low in the US, the modal and median population densities (averaged across people) are actually compared to most places in the western world. The problem is the batshit insane zoning policies of US cities that insist that people live on top of each other in one place and then work on top of each other somewhere far away, and shop on top of each other in a third place.

We flipped the default switch in 10.0, but 9.x shipped with a src.conf option to build with clang instead of gcc. We found quite a few LLVM bugs during this time and didn't flip the switch until we were confident that it would work.

A good example of this is Netflix. Because their infrastructure is designed to support server failures, they're quite happy to deploy random patches against -CURRENT on machines that saturate their network and disk bandwidth pretty much full time and report performance numbers. This has been a really good way of stress testing network and storage stack improvements recently.

The pf in FreeBSD is not just a copy of the OpenBSD code that was then forgotten about. It has been worked on since it was imported, for example adding significantly better SMP scaling in the 10.0 release.

Use the same one. Report every single Conservative Party web site (including candidate web sites in the run up to the next election) as inappropriate content. If enough people do it then some are bound to accidentally slip in to the censor list...

So now it's a high-skill, high-stress job that's earning $26.89/hour (above the living wage in Manhattan, but not by much)?