Don't forget this, btw... The US did not declare war against Germany until Germany made such a declaration first, after the US declared war on Japan. Germany was not bound by the tri-partite pact to honor Japan's "de-facto" declaration of war (to wit, the sneak attack on Pearl Harbor), and it's quite possible that had Hitler not so declared that the US might have gone on to fight a one-front war against Japan only. I (and I don't believe I am alone in this) regard Germany's declaration of war against the US to be Hitler's first major blunder (not counting things before his rise to power, like the Beer Hall Putsch).

So... Microsoft's "research" seems to come from reading competitor's product specifications: my AirPort Extreme has been doing this for my network of macs for ages now - ever since Snow Leopard came out.

This is WoL combined with a proxy. Whenever the target machine is asleep, the proxy continues to respond (in this case) to Bonjour requests. When someone attempts to actually connect to the machine, the proxy sends a WoL packet out and then when the original host wakes up, it will hear from the requesting host and proceed as normal.

The one thing that's a little weird about this is that the AirPort extreme will actually wake the target machine up every few hours to make sure it's still there.

I've been using 6to4 ever since the 6bone shut down, and I've had no problems with it. In fact, it seems to me there are only two possible problems with 6to4 generally:

1. Bastard ISPs could, if they deeply inspect packets, see 6-in-4 packets generally as different or undesirable or whatever and do bad things like they do with bittorrent.

2. The 6to4 anycast default route as a mechanism to get from 6to4 space to the "real" IPv6 space can sometimes send your packets to a non-optimal gateway. The fix for this is simply for more such gateways to be created - preferably one (or more) per ISP - so that the traffic can be routed optimally.

I wanted to opt into Google over IPv6, but when I wrote them they told me to pound sand because I was using 6to4.

Because someone was asleep at the switch.

It used to be that the light turned green immediately after the light the other way turned red. Everybody knew this, and gave the yellow light a lot more respect than they do today.

Then some numb-nut thought it would be a good idea to separate the end of the yellow from the beginning of the (opposing) green. And as soon as they did, people adapted and yellow lights lost a measure of the respect they had before.

And now, there's no going back. It would be unsafe to get rid of the buffer because it's expected now.

Of course, if you never start the computation at all then you never get results.

The terminating condition is knowing when Moore's law will fail.... far enough in advance to know when it is optimal to begin computation.

Um, if you wanted to use a circle as a metaphor for the year, then 2 pi radians would be a full circle, so wouldn't it make more sense to make it the day half way through the year (pi radians)?

Um, that's why they're battery operated.

Um, isn't this what Smart cards were supposed to do for us?

As for the 'waving it in front' part, they have that too - in the form of contactless smart cards. They use them for TransLink around here. I know this, because I took an ordinary JavaCard and waved it in front of a TransLink terminal and it actually responded (of course, it responded, "Tag Card Again," because the correct applet obviously wasn't on the card, but still).

Additionally, 100 years ago, the exact same situation we have today was being played out vis-a-vis recorded music. Only back then, it was piano rolls instead of MP3 files. Playing the part of the big music companies today, were the big sheet music publisher of years ago.

Same arguments, almost word for word.

By that, I mean amateur radio operator. Since the amateur radio service rules include RF exposure safety rules, and we all have to know how to do the math, they will likely be able to reassure you that the situation is safe. The rules for amateur stations are similar to the rules that all other RF transmitting services generally have to follow. Since the condo is not part of the fenced in enclosure where the antenna is, it's part of the 'uncontrolled' space (that is, space where the general public - particularly people not owning or working on the antenna). The exposure limits for uncontrolled space exposure are much stricter than controlled space (that is, any place where a person could be without having the transmitter shut down).

In all likelihood, the antennas in question are aimed such that the energy won't be going into the apartment. How can that be? They have to pay to generate the RF, and they want as much of it as possible to hit the opposite antenna rather than be used to irradiate a nearby condo.

They're selling this unit for a song likely because of the "what if?" thoughts you yourself are having. Educate yourself and turn this into an opportunity to acquire an undervalued property!

If you had used "find my iPhone," you likely would have been able to find it in the snow (yes, I know the GPS isn't that accurate - he'd have made the phone ping and listened for it) and not had to wait the two months.

The first two things I wrote in java were the quintessential '15 sliding tiles' puzzle game and an Othello game. I wrote them in swing. I wrote them not because the world needed yet another implementation, but because it was a fun challenge, and I got some practical experience in writing not only Java, but UI code (in this case, Swing, but the concepts had far wider applicability).

They're still on the net, for what it's worth. Don't expect a lot.

The third thing I wrote was MacXM, though that was in Java/Cocoa. Its follow-up was JXM.

I mention all of this because my advice is that once you've gotten all of that theoretical stuff in your head, the next thing you should do is write something. Even if it's just something for you, it's still something.

Now that's a downgrade and a half.

So you weren't born in a hospital, then?