The biggest problem with most of the devices, which Wink solved, is ZigBee+Z-Wave+WiFi... how do I keep all the years of devices talking. That's what the hub is for.

How much does Wink cost?
The Wink app is free to download and use. The Wink HUB, required for some products, is $79.99. There are no contracts or monthly fees.

And seriously, one week, when we have little to no shopping options to look for alternates? The timing is horrible.

"This accessory is not supported" messages for most of my off-brand Lightning cables. Worked before the update, work with all my phones that didn't have the update, don't work now (this is based on the public beta).

Asus did this with WebWare as well. Looks like it died after 2007, but I could remember that someone did it...

Meant to be logged on as I posted this, not an anonymous coward. That was me who said that...

For those looking for data, try here: http://www.behardware.com/articles/862-7/components-returns-rates-6.html Now, I work in this industry, and so I'm not trying to disparage any particular vendor, but this is the only external datapoint that I know of at this point, and explains some of the frustrations being expressed.

EMC's Syncplicity allows you to have a "cloud" backup that's actually domain authenticated and resides in your own data center. Some of the Dropbox-esque features people want, with the in-house security.

I'm an avid fantasy reader, and started with these books as a kid. I didn't even know the Disney movie (and video game!) existed until years later.

Speaking as someone in the NAND industry...

NAND does not have its own reliability controls on-die. Items such as wear-leveling, file management, and ECC mechanisms need to be handled somewhere. So the options are in software, which would then need to be validated and designed for each NAND manufacturer, die, and process; and would consume CPU and batter power from the tablet OS, or it can be done via a separate off-die controller.

And as to the choice of eMMC, it's a cost/performance/reliability trade-off. eMMC is relatively inexpensive (very small die), and includes all of the aforementioned reliability mechanisms at a low-power, and low-cost method, in an I/O language supported by most mobile architectures (SD/MMC). However, it severely lacks in relative performance to an SSD. The other option is an optimized SSD controller, which may cost many times more, but has much higher performance. The problem is how to include a $100 SSD in a $100-200 tablet BOM... impossible.

In my college program on electronics design, we actually did a lot of system-level programming on 8085 machines. We went so far as to build DAC converters to build volt meters out of computers. What it gave us was the ability to understand the basics of CPUs interacting with memory, signals, IOs, assembly language. That said, with two years of that under my belt, I am no closer to understanding any real-world programming that can get me a job, than had I not taken the class.

Yes, the basics of computers are much easier when you don't have massive clock frequencies adding insane complications to applications. No, programming has nothing to do with understanding what JMP does. Do I think it's valuable? Sure. Do I think it'll make any difference on whether you can call yourself a "programmer?" No way.

Ebay it, take the $150, and go buy a box better suited for what you want. Grab an AspireRevo, hook it up through HDMI, and you're only fronting $50 for something more useful and practical (at least, after Flash 10.1 comes out...)

God of War wasn't AO either, and you had to pound out a sex scene rhythm at one point... not just all sex is AO and removed, just explicit and graphic sex.

There are a lot of posts just like this, so I'll respond to this one.

Web code is simplistic, for sure, but how many hours have to be spent making a page render the same in IE4-8, Safari 2-3, Firefox 2-3, Opera, mobile browsers, etc.

I can code a beautiful page for any one, or maybe two, of those in no time. It's double the work or more to get it to render in all of them accurately. And all of this with solitary HTML/CSS/JS. Now I have be a DBA, I do program in C/Perl/Java/PHP, yet I have respect for the need to actually work knowledgably in HTML/CSS. It's not the code that's tough, it's how different the definitions of that simple code are across the ecosystem.

There's one other reason to choose NTFS: the file system is spread across the drive, versus having a localized FAT table. Unless the wear-leveling on the drive is good (and most controllers for USB sticks are more than sufficient for what they're designed for, but I wouldn't call "good," they're designed for price), you end up with very uneven wear on a finite-life product. Add in that the USB market takes the lowest grade of memory available, and I'd trust NTFS over FAT, generally.

That said, I still use FAT, because as long as my thumb drive works long enough to move my presentation from my laptop to my customer's, it's done its job. I don't expect it to have a long life, and I have an unlimited stream of new drives to play with.