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.

The real trick would be to put your unix-like box behind your gateway, routing all traffic through it. This has the massive advantage of not requiring you to go around, reconfiguring all suspect devices to use a proxy server (if they even can).

I assume this is possible with a mac, its certainly relatively easy to do with linux.

When their glaciers start growing. Duh!

Yup. From the start of the ruling:

"We transferred the case to this court on our own motion. [FN3] We now conclude that the answer to the reported question is, "Yes, where the defendant's compelled decryption would not communicate facts of a testimonial nature to the Commonwealth beyond what the defendant already had admitted to investigators.""

So: don't admit the disks are yours, don't admit you know they're encrypted, don't admit you can decrypt them. (Of course, "don't say anything at all", the old standby, covers all of those, thus once more proving its value.)

That's what you might call a market incentive. Capitalism sees national security and arms export controls as damage and routes around it.

Your attempt to confuse here isn't really helpful.

Google does *sell* Google Glass and Nexus phones and tablets and Chromecast and Nest and soon Dropcams and probably more. They are "Google products" branded and sold by Google as theirs.

Mozilla only has one device that it works on directly, the Firefox OS Flame reference phone. The rest of the hardware you see out there is being made and sold by someone else.

And that's not just true of the hardware. Much of the work going on to extend Firefox OS software into areas outside of phones is being done by third parties for their products.

Mozilla doesn't build hardware. We make software, including Firefox OS. Firefox OS is a completely open platform freely available for any company to build on top of without restriction. There are dozens of companies building Firefox OS-based products today and there will be more tomorrow, covering mobile phones, tablets, TVs, set top boxes, game consoles, streaming dongles, wearables, and more. Some of those companies are working directly with Mozilla and others are taking the code and running with it on their own.

Don't worry about that! They had their own classes of blunders instead. (Every programming language has a characteristic set of problems that come up, and a set of recommended programming practices that avoid those blunders.)

If your compiler is doing that, you should choose a different compiler. Summoning elder gods just because signed arithmetic might wrap around is not a good cost/benefit tradeoff!