Check out the Devspeak videos. Seems like a nice change of pace: http://www.wildstar-online.com/en/media/videos/devspeak/

I ended up buying the Xperia Ray for size reasons, despite the lower performance. If you put a custom kernel on it, it will overclock up to 2GHz (if you're brave). Anyone can safely run with the chip at 1.6GHz (this is what I do). I still get a full two days from the battery even at the speed (i.e. Monday morning until Tuesday night), and the wall charger will top it up from 10% or so in about an hour. The overclock really makes up for a lot.

If the production is anything like the beta, it's even worse than you think. Yes, you have to be constantly connected and you sign in with your Battlenet account. This has obvious disadvantages, but it has the advantage of carrying your characters and settings around with you when you switch systems. I don't mind this so much. What really eats me is the fact that not only do you have to be connected to play, your actions in the game are communicated to and from the server. In other words, every time you press a button, there's a transaction with the server, just like in World of Warcraft. So unlike Starcraft where you could connect on any old shitty connection and then play single player just fine, in Diablo III you will lag even in single player if your connection is poor. It's been a huge problem for me during the beta. It's possible there's something that I don't understand about how to set up my game. Maybe I can avoid this somehow. But if you log in and hit "Start Game" on whatever character while your connection is poor, you'll find the game pretty much unplayable.

But the Earth is much larger than a bowling pin. I'd say that passing passing within a few Earth radii is of us is a fair definition of a near miss.

No, there wasn't.

He might also mean the old DOS BBS client called Telix.

This has to violate the license terms of XP.

Goddamn?

The movements of magnetic north have, on many prior occasions, caused airports to have to redesignate their runways. Since it requires updating of all the charts that aircraft are required to carry (not to mention signage on the ground), it's often deferred as long as possible. Tampa doing this isn't really that significant, although I admit that it's kind of neat in a visual-manifestation-of-invisible-phenomenon kind of way.

Wikipedia subsection on the subject.

According to the gameplay video on the site linked in the summary, the game does have a persistent world. Check at the 1:03 mark, where the words "PERSISTENT WORLD" are plastered across the screen.

They measure the power at the wall and not on the CPU specifically, so there's no 'fraud' going on. Putting processing elements on the north bridge does nothing to gain this system an advantage. Reading the contest rules, they recommend power meters like this: http://www.brandelectronics.com/meters.html

Yes, but the sanity of our judges is canceled out by our ridiculous Human Rights Commissions. For example, it's a human right to not have to wash your hands while working at a restaurant, or get a better parking spot if you're morbidly obese.

In all seriousness, isn't the library of congress always growing? Is its growth rate significant enough that it's a very different size than it was in, say, the 1980s when we heard about hard disks that may someday be able to store an entire library of congress?

This article outlines the various circumstances under which hyperthreading either benefits or impedes performance. While it's true that on average the benefit was zero (meaning about half of what they tested was faster, and about half was slower) there are clearly a lot of applications that see significant performance gains.

It should also be noted that the applications that benefit are ones that would generally be used in Xeon (server and workstation) machines. Further, most of the applications that failed to benefit from hyperthreading are not written to take advantage of many (more than one or two) cores. As applications are updated for "many core" systems, it is likely that the benefit from hyperthreading will become more significant.

In any case, it is far from "established" that hyperthreading has "no benefit."

"Ice Time" is a very valuable commodity in Canada. People will drive for hours on a Sunday night just to get half an hour on the ice. The rink schedules are simply packed. I go to a "free skate" (basically just around the rink in a circle) for two hours on Sunday nights at 9pm. When we're walking out at 11pm, the hockey teams are taking to the ice for a game, which will take 2-3 hours to play.

I was talking to a parent at the free skate while they were resurfacing the ice (they resurface before and after the skate, and once in the middle) and he was saying that he would be back at 6am for his kid's hockey practice. 6am - 2am, resurfacing at least once an hour.

Frankly, I think the 12-15 times a day estimate was conservative, and that the number is probably closer to 20.