I agree that var is bad, and that if you use it you are a bad person; but used well lambda expressions can greatly enhance readability - particularly when used with LINQ queries. Consider the following two tests (code written from memory, it's been a long time since I've done this, there's probably mistakes)

Assert.IsTrue(list.Any(item => item == value));

against

bool matches = false;
foreach(Type item in list) { if(item == vale) { matches = true; }}
Assert.IsTrue(matches);

The first one is obviously a lot shorter, but its real advantage is that it actually looks like what it does with no need to parse loops or introducing tracking variables.

Won't merge? Word has built in merge and diff tools https://support.microsoft.com/...

The singularity of a black hole simply means we can't see that far. It is the point from which information cannot escape. It's not some psuedomystic hand-waving nonsense promising unicorns and fulfilled dreams. It's just the name for a region for which there is no way to discover what is inside of it.

The singularity in the context of technological progress uses the black hole as a metaphor. It describes a point at which technology becomes self-propelling in a manner that makes it impossible for us to project what life would be like then, in a similar way to how miniaturisation and Moore's law have given us a present that couldn't have been projected in the 1940s. People then like to project what it could look like as an interesting exercise, and some of them choose to promise unicorns, but that doesn't make the concept of self-propelling technological advance itself inherently wrong.

Human field of vision is wider than it is tall, therefore our video recordings are landscape , therefore our video display devices are landscape . Unfortunately, when reading there is a cost in time and readability when a line of text extends beyond a certain length, hence why we use paper in portrait, and why some early displays were portrait. But there's nothing stopping you from having multiple portrait windows on a sufficiently large landscape monitor.

In response to the announcement on their Facebook users are lamenting that they can no longer use the site to stream full episodes of both new and classic Who. Clearly the site must have offered streams of full episodes for the users to be upset that they aren't there anymore.

We are seeing the whole story here, /. is just choosing not to cover it adequately. The site was hosting full episodes, which was the main reason anyone visited it. This isn't the BBC using overreaching copyright laws to leverage control over its brand, it's the BBC using the reasonable end of copyright law to protect its right to control the distribution of content.

From the summary:

The purpose of the site was not to let fans discuss their favourite episodes, it was to store and distribute copyrighted material without licence. This is precisely what copyright laws were designed to tackle. This isn't news, this isn't relevant to any serious discussion about copyright reform, this is the system working as intended.

From the summary:

They do at least hint at it in the summary. That said, it's still beyond a joke that they're treating this like an outrage when it's simply the law acting like it should. How can we hope for a serious discussion about copyright reform when so many people take the childish approach of simply demanding to have exactly what they want for free all the time?

From the summary:

The purpose of the site was not to let fans discuss their favourite episodes, it was to store and distribute copyrighted material without licence. This is precisely what copyright laws were designed to tackle. This isn't news, this isn't relevant to any serious discussion about copyright reform, this is the system working as intended.

A 2009 study claim to have managed it. Given the range & pairing requirements of BT though, it does mean crashing a car that you're currently in. Giving the victim a specially prepared CD that will hack the CANBUS half way through their road trip seems a much more sensible idea to me.

I just pass the list to the intern helper-object, and let the environment deal with the implementation.

Apparently this icebreaker is manned by horses specially trained to rescue any livestock swallowed by the crew of other ships.

Actually, the technology that became SQL was originally called Sequel, but that was trademarked so they changed to SQL. So the correct answer is /s kju l/, but that's only for legal reasons, and mispronunciations are as likely to be due to knowing more about the technology and its history as less.

Even PHP has database abstraction these days.

If you're just bouncing, with no additional information it's not an amplification attack, just reflected.