It's a rare drop, sure. The catch is that you have to have your profession skill up a certain level before it's even visible. My engineering is at 450 and I saw it drop once, but I lost the roll to my guildmate, who chose Herbalism and has skill level of 450 for picking flowers. :-(

it's a reference to the Draenai - an alliance race that was introduced in the first expansion.

Yeah... it would be real nice if the general public had access to the source code in some kind of Open fashion regards to browsers such as Firefox or Webkit/Safari/Chrome so that stuff like exploits can be patched, making it would be possible to have tons of eyeballs pore over the code and be able to submit fixes on behalf of the community, or point out bad stuff that perhaps some other developers may have missed.

That would be cool.

the ff addons that I find to be the biggest culprit for memory leaks are Webdeveloper and Firebug.

The christmas rush is a profit gimmick - the games with the most (advertising) visibility generally would get the most cash - this is regardless of the quality of the game.

Blizzard doesn't really play by the marketing rules. Warcraft 3 was released in June '02. Diablo 2 also in June 2000. The first Starcraft was released at the end of March '98.

I would say that those properties have done pretty well on their own without the help of any holiday season shopping boost.

Theora was based on one of On2's earliest codecs. VP6 & VP7 have been far more successful and are even used as the Flash video codecs. If Google is acquiring On2, it could mean that they're looking to open up the formats that have defined Flash as the media player of choice.

(Sorry, this is somewhat offtopic, but it was the first thing I thought of when I saw the comparison between Windows XP and Windows 7.)

I once saw someone here on Slashdot mention that Microsoft should not have shipped a 32-bit version of Vista, opting instead to push only the 64-bit version. While it seemed like an odd statement at the time (despite the fact that my home XP machine was an AMD64 processor), I find myself agreeing with it on Windows 7.

As it stands today, 32-bit Windows is quickly becoming too small for many business and industrial uses, and it's very affordable to build a high-performance home machine with more than 4GB of RAM. (Case in Point.) In fact, with intensive web applications and sophisticated desktop tools (yeah, some of them are bloated) chewing more memory than ever before, it just doesn't make sense to get anything less than 4GB (nay, 3GB if you're running Windows 32-bit!) except for a few edge cases.

Unfortunately, Windows has been kind of lagging on the 64-bit front. By treating it as sort of a bastard child (like they treated all their non-i386 NT versions), Microsoft managed to ensure that hardware manufacturers wouldn't make an effort to support 64-bit windows in a non-server environment. Which is frustrating as I've started bumping up against that once-awesome 4GB barrier.

In an attempt to turn this into a slightly more useful conversation rather than a one-sided rant, I was wondering if I could get some opinions on using virtualization as a solution? With Windows' poor track record as a 64-bit OS, I have been thinking about running a 64-Bit Unix and virtualizing 32-bit windows for backward compatibility. I've already had some success with virtualizing Windows 7 on a MacBook, and have even been able to get desktop integration working. (Quite spiffy that. Though the two interfaces occasionally confuse my wife. She's the primary user of Windows, needing support for some specialized programs with no real alternatives available.)

Does anyone here have experience with setting up a system like this? Do you use Xen, VMWare, Sun VirtualBox/OpenxVM, or some other solution? What do you use as your primary OS? Linux has come a long way, but the upgrade treadmill is still frustrating. Especially with the seemingly regular ABI upgrades. Does anyone use [Open]Solaris x86_64 as a host? Do you have 3D Graphics completely disabled, or have you found a good way to allow all OSes solid and reliable access to the underlying graphics card? Do you bother with mounting virtual shared drives to move data between the OSes, or do you have a home NAS for storing data? (I'm leaning toward a NAS myself.)

Just a few thoughts, anyway. Thanks in advance for experiences & suggestions! :-)

Perhaps the team doesn't want to have to constantly maintain 3 seperate codebases for the same app whenever an OS goes thru a major revision.

Or perhaps because they want users to use it "right now" instead of having them go thru the install process considering almost every machine has a browser on it.

Wasn't Wolfenstein, released in 1992 the first game with 3D graphics?

Not even close. Wolfenstein wasn't even the first raycaster game. It was preceded by Catacombs 3D (also by Id) which itself was preceded by Hovertank (also by Id).

Before those were even a twinkle in Carmack's eye, we had MIDI Maze (1987) and Star Wars Arcade (1983), just to name a few. There were tons of attempts at 3D games before Carmack. He merely popularized the First Person Shooter genre and made 3D Graphics the standard.

The problem here is in trying to patent a trade secret rather than an invention. Patents are intended to cover inventions. Real, working gizmos that operate is a specific fashion. Trade secrets cover processes and information that is of a competitive advantage.

In this case, the two are getting mixed up. The company may have a device to detect certain attributes (which IS patentable) but the fact that the attributes can be measured in order to draw conclusions is inherently unpatentable. If someone else develops a machine for measuring the attributes that works different from your machine... well... tough noodles.

All that can be done is to keep the information a secret. By keeping it secret, it is legally viewed as a "trade secret" which can be contractually protected when sharing with interested parties.

Disclaimer: I am not a lawyer, but I did stay at a Holiday Inn Express once. ;-)

I happen to agree with the GP, and I've written tons of games in the past 40 years. Here's my Atari 2600 version of Lunar Lander:

http://www.pdroms.de/files/73/

Run it through an emulator like Stella to play.

I later ported the game to Flash, but it's not quite as fun as the 60Hz 2600 version. However, you can play it on a Wii! (Use S for thrust if you're on a PC.)

http://www.wiicade.com/gameDetail.aspx?gameID=692

Evidence is presented in courtrooms, not to journalists. Saying, "there's no evidence" is basically a fancy way of saying, "the court has not yet heard the case".

For now we have allegations. They will be proven or disproven in court.

FTFA: "The suit alleges white officers post on and moderate the privately operated site, Domelights.com, both on and off the job."

That was one variation of the term "computer". But as my old fashioned flight computer can attest to, slide rules were often referred to as computers as well.

It's interesting listening to some of the vets from WWII. They'll often talk about their "trajectory computers" or their "bombing computers" or their "landing computers". To the modern ear, it sounds like they're talking about early electronic machines. Yet these references are just specialized slide rules used to "compute" results for a set of measurable inputs.

The Saturn V could lift more than double the shuttle's cargo capacity

I addressed this above. The Shuttle Transport System has better power output, but it has to waste it on carrying a giant airplane into space. The Saturn V was less powerful, but far more flexible. Put whatever you want on top and it gets to space. That often meant the Apollo capsule/command module/lander/moon equipment combo with sufficient velocity to make lunar orbit, but also occasionally meant a huge hulk of steel and solar panels like SkyLab.

The Saturn V boosters were detuned as well.

I'm not talking about detuning. I'm talking about reducing engine output once maximum dynamic pressure is reached. If the SRBs maintained maximum thrust, they'd push the shuttle beyond its structural limits.

From Wikipedia:

The propellant is an 11-point star-shaped perforation in the forward motor segment and a double-truncated-cone perforation in each of the aft segments and aft closure. This configuration provides high thrust at ignition and then reduces the thrust by approximately a third 50 seconds after lift-off to avoid overstressing the vehicle during maximum dynamic pressure (Max Q).

What you're referring to is the resonance problems inherent in the engine vibration of the F-1 engines. i.e. The "pogo" effect. As I recall, this issue is currently the biggest challenge facing the Ares I stack. The Space Shuttle was vulnerable to some pogo effect, but adding dampeners to the LOx fuel lines was sufficient to prevent the effect.