No need for guns; just station a half-dozen guard birds on the roof.

If you can't afford kids, don't have them in the first place.

There are some good cordless vacuum cleaners and hair dryers. No problem recharging their batteries over 12VDC.

Yikes, frostbite is awful. I hope you don't have pain from it! I'm a big fan of dry weather. Colorado's climate is so easy for me - the cold isn't as bad as humid sea level cold and the heat isn't as bad as humid sea level heat. I think the thinner air and generally low humidity make everything easier to take.

The Open Group claims the copyright on the POSIX specifications. If APIs can be copyrighted and this copyright includes all implementations, then it would be problematic for all open source *NIX systems. Of course, they might decide to provide a license that's valid for everyone except Oracle (though writing such a license in a way that's GPL compatible would be very hard, so glibc might be in trouble).

The thing that killed DC in the war of the currents was that step up and step down transformers for AC are easy and cheap to build, but doing the same thing for DC caused a lot more loss (one of the simplest ways of doing it was to convert to AC, do the voltage change, and then convert back to DC). For long hauls on the grid, you want a much higher voltage than in houses. Now, however, it's relatively cheap (both in terms of convertors and in terms of loss) to produce DC-DC converters. USB-C supports 5V (up to 2A), 12V (1.5-5A) and 20V (3-5A). It's fairly easy to imagine 48V between rooms and then a converter in the sockets able to provide USB voltages. You wouldn't want to run a heater or a vacuum cleaner from it, but it would be nice for a lot of consumer electronics.

We're not talking grid back-haul though, we're talking a few tens of metres maximum within a house. I've wondered for a while if it would be more efficient to have moderately high voltage DC room-to-room and then low-voltage DC in rooms. Given the number of things in my house that would prefer a DC supply and so end up with (cheap and inefficient) AC to DC convertors per plug (and especially if you use LED lighting), it seems like it ought to be a win. And now seems like a good time to do it, as USB-C is a consumer connector that can provide up to 100W via something that's designed to be very cheap to produce in the lower power variations.

Top 10% probably. Take a look at a global rich list calculator. You can live very comfortably in a western country with 9% of the world's population being richer than you. If you're in some parts of central or eastern Europe, or a few parts of south-east Asia then you may be near the bottom of the top 20% and still living very comfortably. The '1%' that people talk about in the USA are well in the top 0.1% globally, but 'the 1%' makes a better soundbite than 'the 0.1%'.

Fewer seamen suffer from PTSD than VB coders.

I find it hard to consider anyone who owns a house (even with a mortgage), especially in one of the places with the highest property prices in the world, poor. This scheme seems very odd, because the poorest residents of California are renting, they don't own houses (well, the poorest are homeless), who can't just stick solar panels on top of a house that they're renting.

Okay, I'll give it a shot, then... here's where I find multiple inheritance not just plausible, but preferable.

I have a publish/subscribe model including an abstract-base-class/interface (call it IDataSubscriber) that can be subclassed by any object that wishes to be notified about e.g. data updates coming in from the network.

There are a number of common-case standard responses (implemented as concrete IDataSubscriber methods) to those data updates that are useful for many situations, and I don't want to have to have to rewrite them separately for every subclass, so I make a concrete or almost-concrete subclass (e.g. StandardDataSubscriber) that contains this common logic.

Finally, in my client code (based on Qt) I have a number of GUI widgets based on QWidget or QPushButton or whatever. I want these widgets to react to published data in the standard way, so I often end up with this:

class MyButton : public QPushButton, public StandardDataSubscriber {...}

... and it handles my needs nicely. It's also possible to do the same thing with "just" single inheritance and interfaces as well, or with Qt's signals-and-slots, but AFAICT do to it that way you end up having to do lots of manual method-call-forwarding through proxy objects (or, alternatively, lots of manual signal/slot connecting), which is less efficient, harder to read/understand, and more error-prone.

Maybe this will finally shut up the people who complain that eBooks just aren't like the real thing.

I just hired a smart kid out of school here in MN for 65K, full bennies. Had him as an intern.

The nuclear tests were all for a good cause. Better there than my back yard.