Of course, the usual reason why the case got to the Supremes in the first place is because there were two cases by different Appeals Circuits which conflicted.

Mine did, but doesn't now: their lowest grade plan is now faster than that. The upper tiers might have throttling, but I don't thing the base grade tier can hit the level at which they care.

But then I'm not in the US. We have real competition between communications providers.

Are you sure about that? You seem to be assuming that everyone will be travelling from and to different places and that there will be no concentrations of people attending the same location at the same time. It's been my experience that people don't work like that. I also suspect that the price that these vehicles would charge would make them rather less economic than you think. Unless there's evidence that what you propose would be cheaper than public transport currently is, or that there will be no common locations and times for people to go somewhere, there will be an incentive to have public transport of some form.

I suspect that this difference may be in large part due to the more widespread use of water-based transport in the EU; it's a lot more efficient than even rail (provided you've got a suitable river going in the right direction or are close to the sea, which describes more of the EU than the US).

I've seen a few driverless trains around the world (e.g., in Paris, Copenhagen and at ORD in the US for transfer between terminals) and they usually operate with two sets of doors: one set on the train, and the other on the platform. This keeps people from accessing the track area except when the train is there to let them board. Combine this with obstruction detection when the doors are closing (without which millions of automatic doors wouldn't be safe) and I think we can say that this particular problem is solved.

Or was the GP foolishly assuming that they had to use the existing equipment? That no investment was possible?

Funnily enough, on Stack Overflow! Not all of the security-related questions are overflowing with shitty misinformation. (SO might not be great, but it's better than the squillion shitty places for question answering that preceded it.)

Your audio collection is... not like mine.

You do not have the right because the government says so, but rather because you are a human being. Though that is a principle that is explicitly stated in the US constitution, it applies everywhere. However, it is a right that is made explicit in the EU and where the conditions under which the right may be infringed are perhaps more clearly stated (and better enforced) than elsewhere. There is a danger in explicitly stating rights, in that some stupid people might think you have no other rights — not true! — but leaving them all implicit has other risks in that it becomes hard to say for sure when they've been unreasonably infringed and to get other people to help you out defending them.

Yeah, but getting all that to work when dealing with the reality of BYOD in many organisations (universities have a particular problem with this) is massively more complicated and expensive than ponying up for an externally-signed certificate. Heck, even getting an externally-signed local CA certificate is cheaper. Group policy (and equivalent) works relatively well for desktops and other wholly-owned devices, but ceases to be nearly so useful once you have to deal with anything external, and that's more and more common.

Get with the programme.

Were any of those plants making key inputs for yours? If they were, and it wasn't practical to consolidate that function, then closing them down would have crippled you. Which individual plants make money is one thing, but where there's internal transfer of items between units of the business, the value attached to those items is fairly nominal in practice; it's the overall business that really makes the profit or the loss.

Or maybe they're just incompetent fucks. That could be true too. Hard to say without the full facts, but the fact that bankruptcy hit is strongly indicative.

Take at least one OO language (Java's fussy and bureaucratic, but its a pretty good example of the breed and is likely to be useful after you get your masters), at least one functional language (probably Haskell these days), at least one declarative language (Prolog or SQL), and don't just learn programming languages. You also need to learn about data, about data structures, about algorithms and their analysis, about parsing and compilation, and about concurrency; these are all independent of any programming language.

But computing is well served by not just learning about computing. If you have time, learn about math, stats and logic too, and learn how to communicate your ideas effectively; you'll never get far if you can't communicate with other people well.

Huh. I use it quite a bit when implementing an API. (You hardly need to use public at all inside interfaces.)

I'd guess something like:
        if(target->ThreatRating = ThreatRating::Trrist) { target->Kill(); }

Let that be a lesson to you: Trrist must evaluate to 0, for humanity's sake!

The problem is that it requires a true breakthrough, and there's no way to predict when that will happen. It also doesn't help that we don't really know what intelligence really is; all we've got is lots of things it isn't. I suspect that when someone cracks it, there'll be lots of people going "Is that all?! Anyone could have got that." and they'd be right, except that nobody did and it involves something both trivial and non-obvious. It might also require a lot of parallel processing, which we're still learning how to do well.

As we don't have any handy breakthroughs right now, we should instead study how brains really work and how to make computers do useful things (including stuff like "understanding" speech, "understanding" written natural language, drive cars safely, etc.) Those might or might not make the breakthrough easier, but they'll have other benefits along the way so they're still right to do.

And your grandmother's business too, assuming you want actually communicate that cooking recipe to her.