For some tasks I can understand recycling. I use older hardware to build routers, anti-spam gateways, VPN appliances and the like. Normally these are fairly low-cycle tasks, at least for smaller offices. But I've learned my lesson about using older hardware in mission critical applications. I've set up custom routers that worked just great, until the motherboards popped a cap, and then they're down, and unless you've got spares sitting around, you're in for some misery.

How much do Kremlin astroturfers get paid?

And where exactly are you from? Some of the most accusatory reporting is coming from Europe.

I feel like I just read a Soviet era Pravda article.

"And this picture we see the tin pot wearing Johnny Appleseed and distributing Spam to all the starving earthworms in the New York subway system."

Um, no. We're not going to the moon or anywhere like it. The economy will likely collapse again before the end of the decade. There won't be the money or the resources. Sending robotic missions makes more sense. Sending people is a dumb idea. We evolved to live here. We are expensive to travel and hard to settle. Machines are constructed to do certain things in certain environments. They are more capable than humans in that regard. Send them to get fried by coronal mass ejections.

Except math is almost never actually done that way in practice. Euclid was wonderful, but almost all modern math does not work that strictly (and Euclid really should have been more careful with the parallel postulate -- there's "more than one thing at a time" involved there). Yes, proofs are careful and detailed, but so is, say, technical writing in English. Except for a few cases (check out metamath.org, or Homotopy Type Theory) almost no-one actually pedantically lays out all the formal steps introducing "only one concept at a time".

I don't think you need math even to be a great programmer. I do think a lot of great programmers are people who think in mathematical terms and thus benefit from mathematics. But I also believe you can be a great programmer and not be the sort of person who thinks in those terms. I expect the latter is harder, but then I'm a mathematician so I'm more than read to accept that I have some bias in this topic.

Math is a language. Just because you can frame things in that language doesn't mean that that language is necessary. Recipes are often in English. English is sequencing (words are a serial stream after all). That doesn't mean English is necessary for programming (there seem to many competent non-english speaking programmers as far as I can tell).

Disclaimer: I am a professional research mathematician; I do understand math just fine.

Of course there was a time when college education was supposed to be education and not just vocational training.

The other part of the problem is that math is so diverse. There's calculus and engineering math with all kinds of techniques for solving this or that PDE; there's set theoretic foundations; there's graph theory and design theory and combinatorics and a slew of other discrete math topics; there's topology and metric spaces and various abstractions for continuity; there's linear algebra and all the finer points of matrices and matrix decompositions and tensors and on into Hilbert spaces and other infinite dimensional things; there's category theory and stacks and topos theory and other esoterica of abstraction. On and on, and all very different and I can't even pretend to have anything but cursory knowledge of most of them ... and I have a Ph.D. in math and work for a research institute trying to stay abreast of a decent range of topics. The people who actually study these topics in depth are all called "mathematicians", but if you're an algebraic geometer then sure, you're probably familiar with category theory and homological algebra; if you do design theory and graph theory then those seem like the most useful subject available.

Calculus is perhaps not the best measure however. Depending on where you go in the programming field calculus is likely less useful than some decent depth of knowledge in graph theory, abstract algebra, category theory, or combinatorics and optimization. I imagine a number of people would chime in with statistics, but to do statistics right you need calculus (which is an example of one of the directions where calculus can be useful for programming).

Of course the reality is that you don't need any of those subjects. Those subjects can, however, be very useful to you as a programmer. So yes you can certainly be a programmer, and even a very successful and productive one without any knowledge of calculus, or graph theory say. On the other hand, there may well be times when graph theory, or calculus, or statistics could prove very useful. what it comes down to is whether you are inclined to think that way -- and if so it can be a benefit; if not it won't be the way you think about the problem anyway.

There was at least one American on board.

Because some relatively small number of events may have a conspiratorial aspect does not mean all events do. In this case, it does appear that a bunch of separatists in Ukraine got their hands on some pretty sophisticated hardware and, obviously by accident, blew a civilian airliner out of the sky. Now, that's not as sexy an explanation as secret US operatives standing in the bushes near the separatists, or secret Russian operatives bringing the plane down in an even more elaborate scheme to make the West look bad by making themselves look bad so they can say "Those rotten Americans are trying to make us look bad."

Something like this was bound to happen when relatively poorly trained and disciplined weekend warriors get their hands on serious military hardware. The Russians have been quite keen to back the separatists with weapons, intelligence and some of their own personnel. It would be nice that if they are going to allow these separatists to use advanced AA equipment that maybe they have someone nearby who actually knows how to use such equipment, or at very least to put a bullet in the head of some daft nimrod who thinks he knows how to use the equipment.

"bascially, tt looks like what needs to be done is the PHP runtime needs to be tightned up."

Boy, you could put that on the PHP developers headstones.