I had to laugh at the "Possible GPS navigation" part, since they couldn't even get the GPS to work properly on their Galaxy S line of phones. What makes them think they can make it work properly on the tablet?

The GPS problem on the Galaxy S line has been known for over a month (and acknowledged by Samsung, even) and yet there's no fix for it. I mean, it's not like it's a minor problem with the GPS... the GPS just does not work on most phones, and some even will kill your GSM connection all together periodically.

Possible GPS navigation my arse! How about making a working GPS on a phone before trying to put it on a tablet. Other phone manufacturers have been able to put working GPS units in their phones for years. One would think Samsung might have tested this out before releasing a flagship line of phones.

That's correct as far as it goes... but the bottom line is you can take the best console FPS player in the world and a mediocre to decent PC player will destroy the top tier console player. There simply is no competition between a game pad and a keyboard/mouse combo. Couple that with crappy graphics and console are just ass for quality gaming when it comes to FPS and 4X or RTS games.

The OP was complaining about the secretaries saving to the local drive. If they don't want them to do that, they need to take away the ability, not try to train them not to do it, because it will never happen and it's a never ending cycle. That's all I'm trying to say - change the system to fit the users, don't change the users to fit the system.

I had to deal with a similar situation in the military... I came to the conclusion that users will always be users and if things like this are happening, it's a failing of the IT and/or Software Design portions of the system. If your secretaries are saving documetns to My Documents on the C: drive, you need to change the My Documents to point to the network drive. You need to basically start eliminating/changing the way the users do things that are improper... it really is ultimately a failing of IT to design the system to cater to the users. In the end, you only have to design one system that works, as opposed to training individuals forever. While it takes longer to design a system properly and less time to train an individual user, over the operational lifetime of the system, the cost:benefit ratio for the properly designed system will far, far outweigh the cost of training users (and ultimately failing).

I could actually see a lightbulb go off in the head of an Admiral during a JTF exercise one time when I explained this concept to him. Apparently, the concept of making a system that fits the users, instead of making the users fit the system is foreign to a great number of people, mostly in management and those that make budget decisions.

The public health consequences are a direct result of the laws making it illegal. If prostitution were legalized, licensed and taxed properly, the health consequences go from a drawback to a net asset.

So no, your reasoning is completely flawed. There may be other reasons to outlaw prostitution (though I can't think of a legitimate one), but health concerns are not it.

Lightroom has a few critical problems that make it exceptionally problematic with the workflow. For one thing, it's noise reduction algorithm is atrocious. You really need a dedicated NR system in place, like Noise Ninja or such. The one in Lightroom is literally probably the worst one I've used. DxO Optics is fairly decent and features a large database of lenses for correction. Bibble 5 is nice and integrates directly with Noise Ninja, which is awesome - however Bibble 5 is also buggy and crashes a lot - it also has LOTS of trouble dealing with large projects. If Bibble 5 supported DNG and was less buggy it would be the best program out there.

Anyway, you need to do a bit more looking around - Lightroom 3 may address some of the issues with Lightroom 2.x series, but the 2.x series has too many flaws to be the one and only workflow program you use, sadly.

Wow... do you guys arguing about crossing the "event horizon" of a black hole even understand the basics of it?

With a large enough singularity at it's heart, you wouldn't even realize you had crossed over the Schwarzchild radius - there would be no specific difference from one moment to the next, besides the increase in gravitational pull increasing at the same rate it's been increasing as you approach the singularity from outside the radius (inverse square). The Schwarzchild radius is just a mathematical boundary, it's not a physical boundary.

If you crossed the radius on an tangential orbit, you could conceivably orbit the singularity within the radius for millions or billions of years, living out your life aboard your vessel in your personal reference frame for as many years as you live, watching the universe speed past you at an apparent accelerated temporal rate until the ultimate heat death of the universe consumes you, your vessel and your local singularity as well. There's nothing special physically about the event horizon of a black hole, besides the fact that it cuts off two way communication with the outside universe. Beyond that, it has no effect on anything else. It just so happens that many of the Shwarzchild radius limits of singularities are so small that crossing them puts you into a proximity of the singularity that is lethal. That is purely coincidental though.

Your Foscam example sounds like and/or should be superceded by the Trendnet TV-IP110. It's $50 bucks for the wired version and $70 for the wireless version, I believe it runs linux, you can remove the IR filter from the lens and get wicked awesome low light performance (at the expense of proper color balance), has all the features you mentioned, etc... I looked into getting these cameras in bulk from the Chinese manufacturer, but for anything less than 500 pc, the Microcenter price of $70 for the wireless version is less than the bulk price direct from China. Removing the plastic shell, you can probably shoehorn the board into quite a few discrete places. It's a pretty good camera for $50/$70.

But shocklingly, I've purchased a couple motherboards in the past 6 months that still require a floppy. I was like WTF and had to dig around in a box for a floppy drive. Who the hell still requires a floppy in this day and age? I don't recall what manufacturer it was but I can tell you I'll not be buying another motherboard that requires a floppy to update the BIOS. Thankfully I had a spare box of HD floppies in my drawer, but come on... really? 2010, brand new MB and I had to find a floppy?

No we didn't. I remember as early as 1988 thinking that 1.44 MB floppies did not have near enough storage since downloading some of the new games, like Space Ace, took up 6 floppies and it took forever at 2400 baud. I also remember thinking that I hoped I had enough floppies to store it that wern't bad... because at least 20% of the HD floppies in a box always turned out to have some defect.

So no, 1.44MB floppies in the 90's were anything but "generous" when it came to storage.

Haha no kidding. I had an instructor once that taught the A+ certification class as well as bunch of other computer classes, but when I asked a question about Big Endian vs Little Endian in regards to one of the test questions on significant bits, he had no idea what I was talking about and had never even heard of Endian-ness. It was at that point I discounted just about every authoritative thing he tried to say in class.

As a point of fact in this context, yes that is what I am saying. Again, I ask, why re-invent the wheel? If the tools and know how are already there, it seems kind of illogical to throw that all away and start from scratch.

I feel that you may be mixing up facts here and your statements seem to be leaning towards a belief that only one side can have good and bad hackers. Just because there are good hackers in Homebrew does not mean there are no good hackers in Pro-pirate. Just because there are poor pro-pirate hackers does not mean homebrew has no poor hackers.

Well... by this logic then we can say Homebrew hackers suck at it as well, since I can produce for you lots of actions, code and consequences of poorly programmed homebrew as well.

"Not as good as X" and "Everyone Y Sucks!" are two entirely different positions. As a group, I would say your statement above is true, but that is very different from saying all pro-piracy advocates are crappy hackers.

Ah, now we have a legitimate talking point. By this particular definition, your argument carries more weight. However, I would counter with the fact that piracy is, generally by it's very definition, a dangerous "occupation." I would not expect the piracy aspect of consoles to be as safe, sane or elegant as other forms of programming. Piracy, like it's sea going legacy, is a dirty business... expecting it to be clean or judging piracy against the standards of the Navy is a bit like comparing apples to oranges.

Again, I ask you why should the pro-piracy advocates care? The very nature would seem to suggest that caring whether or not it bricks some idiots console is somewhat redundant in this case.

You make homebrew software because you want to make homebrew software - so the act of making it is a labor of love in and of itself. A pirate wants to pirate games - how that happens is secondary. The primary goal is a free game, if you can use a crow bar to get that game, why use a gold plated screw driver?

You fall into the trap a lot of programmers fall into (and I've done it myself) - you want to make a Cadillac when a Kia will do.

I agree with you here and it disappoints me greatly as well.