Ebola is only contagious when the symptoms are present , NOT during the incubation period. The symptoms of Ebola are pretty pronounced, so if you see someone projectile vomiting and bleeding from their eyeballs, steer clear, but otherwise you should be alright. From the WHO Ebola FAQ:

I was referring to Neymar specifically -- he got a fractured vertebrate in the game against Columbia and had to sit out the rest of the World Cup.

Of course, when you get kneed in the back and get a fractured vertebrae, not much acting is required.

4.8 was also the first GCC version that (more or less) had full support for C++11. It's not terribly surprising to get more regressions when adding (many) new features.

I read the article/rant, and he's bitching about the complexity and time required to learn and use modern frameworks and tools, not so much about planning and management. The summary is a bit misleading.

I think part of the problem is that "programming" is itself so diverse. If you were to be a graphics programmer, you would certainly need your linear algebra, geometry, etc. If you worked with scientific computing, you'd need even more math (e.g. differential equations, statistics, etc). If you worked as a DSP programmer, you'd need to know calculus (and then some). In contrast, web development doesn't really require any of these. However, they all involve "programming", and the people writing the software can all be called "programmers", even if one's writing a website (no math) and another is doing a fluid dynamics simulation (lots of math).

These vials are from over 50 years ago. Your comment would have made more sense if meant facetiously. From TFA:

Tell me again what role Obama had in this?

I was in Paris just last week. There were no "locked down" monuments, and there were no armed personnel patrolling the streets. There were some military-types at the Arc De Triomphe, but that's because of Bastille Day celebration preparations -- that is, they were there for a celebration, not for a patrolling. You're spouting nonsense.

Well, Lois Lerner was appointed by Bush in 2006.

Their OpenCL drivers are pretty bad. Completely arbitrary changes can have huge impacts on things like VGPR usage. Optimizing an OpenCL kernel on an AMD card is like black magic. Not that I'm praising NVIDIA here, they're still on OpenCL 1.1...

Or... if you're using C++, use a Standard Library container? They all keep track of their sizes, and can perform runtime bounds checks (by using say, at() rather than the bracket operator). Or Write your own class with an array member and an accessor that does bounds checking. It's not difficult to do. At all. And templates aren't meant for addressing buffer overflow problems, or as a replacement for raw pointer (use STL containers). Or garbage collection (use RAII). I get the feeling you aren't too familiar with C++?

Just in case this confuses the submitter, the actual title is "The Art of Computer Programming". And IIRC the code examples aren't in Pascal, but rather in "MIX" assembly, which is a hypothetical language for a hypothetical machine. Also, be forewarned that it has a steep learning curve...

Not sure if I'm missing the joke here (if so, apologies), but just because the book title is "Exceptional C++" doesn't mean the whole thing is about exceptions.

Exceptions are covered for a few chapters in that book, but some of the recommendations aren't really relevant anymore; C++11 deprecated many of the problematic parts of exceptions (e.g. exception specifications), and much like valarrays, no one really used them anyways

Well, C++ threads and the new memory model would take more than just a little more typing. Same for rvalue references.

Some operators shouldn't be overloaded (e.g. &, && and ||), but good luck writing any non-trivial container classes without overloading the assignment operator. You may think you're not overloading these, but the compiler is simply auto-generating them for you since you didn't provide one (namely, copy-assignment operator and move-assignment operators). As with any language feature it can be abused, but they can be quite useful when used judiciously. (i.e. if you're writing a Matrix library, you'll probably want to overload the arithmetic operators).

It's true that there are pitfalls to using templates, but I think you're grossly overstating their dangers (while ignoring all their benefits). You can do some pretty amazing things with templates; in the least they reduce code duplication, and at best they allow compile-time polymorphism, better error detection, and a whole different paradigm for using C++ (metaprogramming can pretty closely resemble functional programming).