My son contracted Kawasaki Disease in 1987 when he was 4. It was a terrifying experience as the doctors could not explain what was causing his symptoms, including a fever of 104. The poor kid underwent spinal taps and more. Eventually he was transferred to Boston Floating Hospital for Children where they concluded he had Kawasaki. There was no test for it - it's one of those "process of elimination" diagnoses and not all who have KD have all of the symptoms. At that time, there was no known cure but my son was enrolled in a random trial of gamma globulin infusion and, thankfully, the dosage he was assigned turned out to be the one that worked the best. He recovered and tests showed no lasting heart damage.
At the time, there were many wild theories as to what caused it. One of the more prevalent notions was that it was triggered by carpet cleaning chemicals, since debunked. This paper smacks to me of "correlation does not equal causation". I'm especially dubious about the supposed geographic origins given that incidents, while clustered around metropolitan areas, were not confined to the west US coast (we live in New Hampshire.)
Over the years I have read many articles and research papers about Kawasaki Disease. I don't think we're any closer to an explanation than we were in 1987.
Intel inherited XScale from DEC, which called it StrongARM, as part of the patent lawsuit settlement that also netted Intel DEC's Hudson, Massachusetts chip fab. Xscale actually did quite well for Intel, but as you say, they sold it off to Marvell.
It's done in software with hardware assist - Intel calls this technology "Houdini". Most Android apps are Dalvik which Intel has an X86-optimized implementation of. The translated apps run quite well for most purposes, but yes, there is a performance penalty. I did run some games but probably not the really compute-intensive ones. I found the performance overall quite good - at least as good as my iPad 3 - and to most users the choice of processor would be transparent. For apps which are ARM binary, a growing number are also providing X86 binaries.
Intel-powered Android tablets can run almost all Android-ARM apps. Those that are native ARM apps are handled through binary translation. It works very well. I've used a Dell Venue 8 (Intel CloverTrail+ Android) and did not find any apps that wouldn't run just fine.
I agree - I've downloaded the movie twice from Flixster. Anyone who thinks that a DRM-free download would be provided is dreaming. WB is offering to pay for downloads from other services such as Amazon and iTunes. The OP reads to me like a lame excuse to justify piracy.
Yes, some number of KS backers are having trouble. I know at least one who hasn't received her code. But it reads to me as if WB is trying to do the right thing, on top of this unprecedented same-day digital release.
You're not. Credited in the titles as "55MPH Briefcase", but I don't think Jittlov ever got it going that fast.
If by "lumps of stainless steel" you mean Joulies, you missed that the Joulies have phase-change-material inside - probably the same stuff as this mug. This is why I said it was the same trick.
Yep - as jcochran says,it's just a repackaging in a dedicated mug. The Joulies web site says:
"Their polished stainless steel shells are full of a very special phase change material (an ingredient in food) that melts at 140F. When you put them in your coffee this PCM begins melting, absorbing a LOT of heat in the process and cooling your coffee down much faster than normal.
"Where does all that heat go? It’s stored right inside your Coffee Joulies. When your coffee reaches 140F (the perfect drinking temperature) the molten PCM begins solidifying again, releasing all that energy back into your coffee to keep it at a comfortable and delicious drinking temperature. The more heat you feed your Joulies, the longer they’ll keep your coffee warm."
This is just the same approach as Coffee Joulies, which is a former Kickstarter project. I have a bunch of these, they work well. No need for a custom mug.
The Intel compilers do NOT "phone home" for licensing. What they do "phone home" for is to send anonymous usage data. When you install, you're asked if you want to opt in to this - it is not enabled by default. Licensing is done entirely locally for single-user licenses. See http://software.intel.com/en-us/articles/software-improvement-program for more information.
There's more to be annoyed about with this ad (which I have not seen, but I read about in the Globe). If the ad has Wahlberg saying "This is New England", then by "New England" they mean Massachusetts (Boston excluded), Connecticut and Rhode Island. Verizon abandoned northern New England (Maine, New Hampshire and Vermont) years ago, selling off their business to tiny Fairpoint Communications. Fairpoint, which has finally got most of their accounting issues straightened out, have admitted that while they will continue to serve existing FiOS Internet customers (TV was not offered), they are not expanding it anywhere. At least I got FiOS Internet while Verizon was building it out.
I don't know much about it, but my employer, probably a larger company than yours, specifies that we should use EMC's Syncplicity Enterprise (http://www.syncplicity.com/products/enterprise-edition) for secure cloud storage. It offers the option of keeping the storage in-house. Worth a look.
Yes, the side stories definitely add depth - I agree with you there. As for Redshirts, I would have been happier if he had stopped before the three codas. I had not read Old Man's War or, I think, much else of Scalzi's.
Does the "novel" form of the book just concatenate all of the serial chapters, or is the "re-establishment" text reminding readers of what happened before removed or thinned out?
And yes, I see I mistyped the name of the book in my initial comment.