TellarHK

Yes, I would very much like to have this.

I have a pretty good mix I use right now when testing things. Preferably, I use the CD or lossless compression version, to make sure things are tuned just right.

Dethklok: "Laser Cannon Death Sentence", "Mermaider II: The Water God", and "I Tamper With The Evidence At The Murder Site Of Odin". You want bass? You want Dethklok.

Devo: Pretty much everything on the new "Something for Everybody" album. "Sumthin'", "Fresh" and "What We Do" are the standouts.

Electric Six: The whole "Kill" album. Like Devo, there's a lot of crisp, clear stuff going on. But the electronic distortion is a bit lighter.

Metallica: The "S&M" Album is the one to hit here. Michael Kamen brought his A-game to the composition of symphonic work with the heavy hitting of classic Metallica, with none of the band's later sellout-ness. "Fuel" and "The Call of the Ktulu" work fairly well, and the crashes during "No Leaf Clover" jump out nicely.

I took a two-week trip to Korea, and needed a new camera so I picked up a DSC-TX7. That model isn't waterproof, and not nearly as rugged as this one sounds, but it'll shoot 1080p @ 60fps if I want it. I'll say it was an incredibly great thing to have on the trip, small enough I could take it anyplace and good enough that my pictures looked great. I even shot a little bit of video, and the clips came out quite well.

Here's an example of some video in 720 mode that I shot with it while I was there. Be warned though, it's of eating live octopus.

http://www.youtube.com/watch?v=GqtCWGi3b9U

Ah, laptops. My first one was a Toshiba T1200. Four bit black and white! '286! 640K! Mine even had the optional backlight and 20 meg floppy disk!

It was a tank. I have no idea what finally happened to it, it's just been ages. I think the power supply blew out one day. Or maybe I gave it to a friend.

I remember that my best use for it was the Telemate terminal program. Ah, MUD's, my first addiction.

I so loved the endgame of PQ4: Open Season. It was just a brilliant example of a turn of events you never expected, immediately followed by a moment of epic greatness when you solve the puzzle. Lots of chances to screw up, but it went well for me on my second try.

Whenever I think about great game endings, that's one that comes to mind.

"Aaaaieee, aiieeee, aiieeee, aieeee!"

@Herman Melville

As someone with an iPad, these are quite useful to me. I trust reviews of apps here, even if they're just brief ones. It's a good way to see what's out there.

And if people want specs on the iPad, Wikipedia's only a quick type away.

The biggest flaw with the Nexus One is the pricing scheme currently in use, and the lack of ability to get your hands on one in a store. Eventually, those will change, I'm sure, but I still don't believe Google has ever intended for the Nexus One to be anything more than a trendsetter for Android developers. I might be proven wrong eventually, but the indicators right now are placing the N1 in a pretty unique market segment all by itself.

When I was deciding on a new phone to get away from AT&T's horrible signal in my new house, I decided to go with the Droid. The N1 was something I could afford if I wanted to wait for the Verizon launch, which I figured to be just over a month away, so roughly two weeks - but the hands-on with the Droid sealed the deal.

And for the record, I think the Nexus One on Verizon will be launched this month sometime, but not before next week. I suspect Verizon timed their BOGO sale on Android phones to lock people in before the N1 released on their network, and since I got my Droid the first day that sale started I bet it'll be not long after my 30 day return is up.

@StickyD From all indicators, including the addition of the rest of the US domestic carriers, I still believe you're incorrect in assuming that Google wanted a serious chunk of market share. There are a lot of things that have been learned by companies like Apple and Microsoft in regards to handsets, and Google is smart enough to realize those lessons. If Google had wanted a chunk of market share to compete with Apple directly, they'd have started with a Verizon phone priced to match iPhones at the same price point. There's no other way to properly compete with Apple if you want a stand-up fight.

Instead, Google decided to release a "flagship" phone for developers and the tech-savvy, while encouraging other companies to step up and meet that line. This way, they don't piss off Motorola by coming across as a threat, and they gain goodwill from the people who will eventually see a slightly less fragmented Android than was probably going to be the case prior to the N1's launch. Within a few months, you don't see a 1.5/1.6 device launch for over $150, and I'm including tablets in that. 1.5/1.6 will be under $100-150, and the odds are that you'll see 2.0/2.1 in that price range as well as the requirements aren't that much worse.

What people aren't seeming to realize is that Google has never wanted to compete with handset manufacturers directly. The goal they've seemed to have with the Nexus One was to try and bring some kind of benchmark for developers to work with - since Developers would be a big target market for Nexus One sales - and thereby keep the development of Android software on a more even keel.

One of the huge advantages the iPhone still has in the market is that when you buy an iPhone, you know that there won't be a new version - for at least a year - that leaves you behind in the area of application compatibility. Developers love a stable platform, and that's one thing Android isn't.

Google isn't in the handset game for numbers.

What's been frustrating for me, is that starting with Borderlands my otherwise-stable system decided to occasionally crash and shut down in the middle of a game. Nothing in the event logs, nothing in the game logs, just a sudden momentary freeze, the lights on my USB peripherals go out, and then the monitor loses signal and my machine goes silent.

This is an Intel X38 chipset system running a Q9400 with 4850's in Crossfire mode.

Strangely, the problem also started kicking up with Dragon Age: Origins. So I'm not going to say this is a Borderlands issue, rather than some kind of Win7 / x64 / Heat issue that's popping up.