Also note this was central air he was investigating, not climate control for an individual room, so the units were about ten times that size.

No. If you are using individual memory allocations in C/C++, and overrun your array bounds, the MMU will kick back an access violation and the application will segfault. If you're pre-allocating one giant contiguous memory space to use for all your data, this protection no longer exists.

Maybe five years ago. One of my coworkers was investigating buying a new heatpump. The single-stage heat pumps he was looking at were only sufficient down to around 15-20F, after which he would take a serious efficiency hit as they kicked over to heating coils. He was trying to figure out whether it would be economical to spend the money on a dual-stage pump, or spend it on the few days out of a typical year we have single digit temperatures.

In most cases, one would segfault due to a memory access violation rather than escaping the bounds of their array. When you're pre-allocating a big chunk of contiguous memory, and letting 20-30 independent processes simultaneously use it, those protections are no longer in place.

Professionally, nearly all the bugs I see are simple typos (which you get regardless of your paradigm), logic faults dealing with real-world mechanics (more physics than programming), or buffer overruns (insufficient bounds checking, combined with a multi-process, shared memory framework). Everything else typically gets caught during a compile.

Screw luminous efficacy, nearly all of the "better" bulbs simply look like shit. Why can't I pay an energy premium to get the output spectrum I want?

Only a very expensive multi-stage heat pump is going to be able to heat a home to 70F from a -40F source. Everything else uses resistance heating to make up the slack on very cold days.

Do you have cheaper gas furnaces instead?

What bad habits? Logic of whatever type you want to implement is inherently sequential. Unless you want to delve into the complexity of branch prediction and predictive computation, it is the basis of all programming. The secret to parallel programming is nothing more than finding independent sequences of logic within the program, and arranging them such that they can be run concurrently.

BD's biggest issue was always, and still is, a power source. Their packbots that are supposed to support foot troops in the field need to be stealthy. You can't be stealthy if your very operation requires a noisy gasoline engine.

Then they can sell ads for medical services, home repair services, security services, law services....

He means... if someone is going to rob his place with a gun, he would rather just see them rob the place and deal with the criminal suit and insurance claims, than having a shootout between the robbers and a good samaritan.

Considering GitHub is based off using git, every previous contributor already carries a complete download of the whole thing, including a history of all past commits and branches, at all times. At most, they would lose the handful of commits made since their last fetch.

If they can refuse service to anyone carrying a firearm, and can call the police to forcibly remove you from the premisis if you do not remove yourself, how is that any different from forbiding you to carry a firearm into their store? It just seems nitpicking on semantics at that point.

It's this wonderful, accurate, precise pointing device, that should be packed with every laptop, and used if at all possible.