Entangled photons are used to create quantum macrame.

If I needed one of these for myself, I would sincerely hope that the hospital could afford better than an entry level cranky 3D printer. It only works in this context because they're experimenting and because a scaffolding does not need to be very precise.

In some ways, 3D printing gets used because it's a way to promote 3D printing, even if you could get something cheaper and faster by just having someone carve the same thing out of styrofoam. Makerbot is like Arduino, hyped enough that people think they're intended for more than hobbyists.

BBC still uses them. Probably the most important site left for me that does.

The only person I know who regularly uses an iPad is also a small plane pilot. It seems like a good solution for that environment. Easy enough to put on the passenger seat or to use in your lap to follow maps and update plans, slides into a backpack, etc. Mostly not being typed on, but you can when you want.

The chess program in question uses the BIOS of a Bochs emulator, which is not included in the size calculations.

How about Forth, which can usually result in smaller code than 8086.

I'd go for a Forth version of Chess to really get small code (assume the Forth interpreter is in ROM which isn't cheating since these tiny demo programs use ROM and BIOS as well).

Today though "bytes of RAM" is vague. A lot of chips have very tiny RAM but a (relative) lot of Flash. Ie, the Microchip PIC has instruction lengths of 14 to 18 bits, so these don't even fit into common notions of bytes.
Then again the instruction set you work with is incredibly important as well. Faster is not necessarily smaller here. Also if there's ROM you can leverage that (the program in question most definitely uses the BIOS for a normal 16-bit 8086, the Sinclair also had ROM).

Not necessarily.

Jobs' brilliance wasn't in his management, it was in his design sense, personal charisma, and knowing when to throw his company behind developing and pushing a new product (OS X, iPod, iTunes, Tablets).

Tim Cook doesn't have the same epic level of charisma but that could change, and he clearly hasn't screwed up the management part, but we've yet to see his signature on the design and product fronts. I think you can call Apple Pay and the iWatch products of the Tim Cook era so their success will be the first real test of whether he can keep the Apple innovation machine turning.

You do see that there's a fundamental difference in the business of oil and Apple, right?

The oil guys are, basically, taking stuff out of the ground and selling it to you. Their profits derive from carefully controlling the supply so that there is always a shortage. So that their customers are always competing for the privilege of giving them money. People give money to the oil companies because they have to.

Apple is in the business of creating technology that didn't exist before. They're moving society, if not culture, forward, and making the world different than it was before. Their profits derive from being more creative or more fashionable than other tech companies, not from artificially restricting supply (much). People give money to Apple because they want to.

Something worth considering. We associate snow with cold, so it's tempting to see more and frequent snowstorms as disproof that the planet is warning. However temperature is only one of the constraints on snow. The other is moisture.

I have lived here in Boston over fifty years, and in the 60s and 70s the December climate was bitterly cold and *bone dry*. In recent decades there has been a marked tendency toward warmer AND wetter Decembers and Januaries, and thus frequent significant snow storms in December (almost unheard of) and January (rare until the 90s).

This storm was particularly intense, and in my town got two feet or more. This has happened on six prior occasions, once in 1888, and five times since 1969.

That you know of. Besides, I'm sure you've had many that you've caught during the standard code -> compile -> run -> segfault -> debug cycle, but the more subtle ones are harder to trigger.

Depending on what the code is doing and what kind of legacy cruft you're dealing with it's not always trivial.

More likely the other devs feel like it's bad form to drag the names of past contributors through the mud in public. Particularly when the reviewers missed the bug as well.

VoIP still requires some form of service to the house, and that's almost always copper in rural areas.

Borrowing and spending their way out of it, combined with a national past time of cheating on the taxes. Combine with politicians elected based on angry backlash instead of logic and there's going to be a lot of upcoming economic troubles to make austerity look like the good old days.