jbester

The original 747-100 /was/ spacious on international flights, the upper deck had a lounge and a piano. This wasn't due to some bygone era where passengers weren't treated like cattle, it was due to the underpowered JT9D-3A engines.

Without sufficient power, the airlines lowered the amount of allowed weight on allowed on international flights and thus the seats had better spacing. Later models starting form the -200 model had more powerful engines so they crammed in more passengers - both in coach and in first class.

Not sure I buy either of the metaphors. Silver has industrial, scientific, and commercial (i.e., jewelry) applications that create demand and use the commodity. Bitcoin, on the other hand, does not. It's just used as a transitional currency.

Historically, spikes in income inequality have been a harbinger of a recession - the theory is it can indicate misapplication of capital. In that investment income is outpacing growth in the underlying economy (using worker's income as a proxy). Not sure how true it is in the era of multi-national conglomerates and outsourcing.

I'm guessing it's aimed more at the embedded/system programming crowd. Visual Studio is a PITA when you aren't targetting Win32. Right now we use eclipse which has pretty substandard C++ support.

Technically, he's charged with espionage and giving aid to the enemy. With the stated motive of "sparking a public debate" regarding current war policy, a more targeted leak would have achieved the stated goal, in line, with, say, the pentagon papers or the AT&T/NSA leaks or even the his own later leak of the gun-cam video.

I have a hard time believing the flagrant and wanton release of material was and is not suicide by Court Martial.

Light on dark can be really hard to read for anyone with a pronounced astigmatism.

The background color bleeds into text dramatically lowering the contrast. On computer displays, black on pure white can cause the same issue to a lesser effect. I find black on a pale color is optimal.

Looking at the code, UDP/Broadcast is used only for negotiation. After negotation, a TCP socket is used for the actual transfer.

It's neat. I noticed a couple of subtle bugs.

1) The code assumes both the client and the server have the same endian. This can be issue since a uint32 is used for both the synchronization code (BCP_CODE) and the port. This can easily fixed with htonl/ntohl conversions.

2) it assumes both the client and the server define int to be the same size (may or may not be true based on compiler/processor/OS combinations). If you use stdint definitions, this typically won't be an issue.

Sounds similar to NT (No Text) on usenet...