The vast majority of their users aren't especially smart when it comes to technology. They're essentially office workers - they don't give a stuff about the underlying format, they only care about being able to do their job.

There's actually a standard for writing in C++ for (embedded) safety critical systems, created for the JSF. It exists partly because they were finding it increasingly hard to recruit engineers who knew Ada (or had any interest in learning it).

The main reason to move to 64-bit isn't memory, it's address space. Some other useful things falls out of it in a co-incidental kind of way too, like more registers (which are nice for tight loops).

1994, actually; "Intelligence Services Act (1994)" to be precise. Though GCHQ has been around since the early C20th.

Said act uses wonderfully nebulous language that basically comes down to "we can intercept anything we want because we say so".

The main difference is LTO tapes (and similar) are actually designed so they can be used for archival storage (in the region of 30 years). Hard drives just aren't. If you can get a drive that's been sat in storage - no matter how good - for 20 years to spin up then you're very lucky.

My reading of the sentence was "European and Asian suppliers along with only one US supplier, Tesla; the other US suppliers will just do their own thing."

Except browsers can actually send a header that lists your preferred languages, in order. Chrome can actually does this, although it's buried away under "Advanced Settings". Google just don't pay any attention to it on their servers (apparently).

I'm guessing dogfooding doesn't apply to shitty UI elements :)

My suspicion was Java would be more or less identical, but I don't work in Java so I wasn't 100% sure.

I don't know how different Java is to .NET in terms of exceptions, but with .NET you get an SQLException thrown, but the Message property would just contain something succinct like "Incorrect username or password". There are also a properties giving you access to the actual error codes from the SQL Server. You can also still look at the StackTrace property to get the full stack trace if you want.

The problem with OpenSSL Rampage is that a major part of their approach is basically to rip everything out of OpenSSL that isn't relevant to OpenBSD, which is generally the code relevant to platforms OpenSSL supports but OpenBSD doesn't.

Access to space has always been a pissing contest. You would even be in space if it wasn't.

Chapter 23 of the Swedish Penal Code is titled "On Attempt, Preparation, Conspiracy and Complicity".

They're SO-15, they're a specialist armed unit (formed when they combined SO-13 with Special Branch). They only get deployed when they explicitly need armed officers.

Also we don't have "metro police", that would British Transport Police, who are responsible for policing railways nationally, railway property, London Underground, and various other things. They're not routinely armed.

Alternatively they're really good programmers who got explicitly told "make this run like shit off a shovel and don't worry about portability - this will only ever be on PS3". You can say "but we should really write portable code", but if SMT still tell you to ignore portability then you're left with either doing what you're told or quitting.