“Bad drivers will at some point need to improve their driving or accept [having] to pay for the real risk they represent”
Snapshot can't measure driving quality. It measures speed and distance travelled and sudden stops. Presumably if I'm driving at night and take a longer route going 75mph on a wide-open freeway, instead of driving 35mph on the shorter twisty two-lane country road with far more hazards from drivers crossing the center line or deer jumping into the road, Snapshot will penalize me for it. Again, screw that.
Speaking as someone who's still struggling with the extensor tendinitis he developed as a young programmer over 15 years ago, with hundreds of nights of pain and hundreds of thousands in lost earnings as a result...
First: It's a natural hacker impulse to focus on keyboard layouts and hardware and other fun toys like that. Resist that urge. The importance of that stuff is tiny compared to good overall ergonomic habits, good posture, taking breaks, and managing tension. Get all the help that you can on those issues. Watch your own habits. Have someone else watch you. Make adjustments.
Second: Having said that... when I was first having hand trouble, I switched to Dvorak. This was, for me, a very poor decision. As you've noticed, Dvorak overloads the right pinky finger, which is a bad idea on a typewriter, but a horrible idea on a computer keyboard where other often-used keys are on the right edge of the layout.
Moving the entire arm to hit Enter and other right-edge keys with a non-pinky finger helped some, but not enough. After a couple weeks of increasing right-pinky pain, I simply swapped the L and P keys, so the commonly-used L was on the left index instead of the right pinky.
The L/P swap helped with the overloading, but exacerbated my second problem with a new layout, which was greater tension while typing. Even though I felt comfortable with Dvorak on a conscious level, I was still sometimes tensing up before keystrokes as my fingers weren't sure which way to go for an extra few milliseconds. And I was still having to use QWERTY keyboards often enough that I couldn't completely banish that muscle memory. Eventually I just switched back to QWERTY. More finger-mileage, yes, but is finger-mileage really the issue? It wasn't for me.
Third: No, really. Spend your time on the annoying difficult-to-scientifically-analyze meatspace issues like posture, not on keyboard layouts.
I've been using WiTopia a little over a year and had no problems with it.
BoingBoing recently posted a link to TunnelBear, which has several positive reputable reviews.
"Obama 'will have a 50 cal in the head soon'". In my books, such a line only amounts to a threat if there's a reasonable possibility of its execution.
So if, for example, the person saying it owns a Remington 700 ML
Oh, wait... he did.
Of course Twitter refers almost no traffic to news sites - Twitter sends traffic to bit.ly and the like, which then redirect to news sites. To a lesser extent, so does Facebook.
Looking through the original study, they don't even attempt to address this issue. Remarkably shoddy work.
A new econobox 15" laptop is not even close to equivalent to a three-year-old high-end ultraportable. Or a three-year-old 17" gaming laptop. Or a three-year-old tablet PC. Or even a three-year-old high-end 15" office laptop. It's dishonest to suggest that because the new econobox has comparable benchmarks, that it's a comparable system. Laptops are more complicated than that. The econobox has nowhere near the same utility.
If you disagree, try lugging it through an airport instead of the older ultraportable, or try holding it in one hand to take inventory instead of the older tablet. See how much good the extra PCMarks do you.
Also, what kind of laptops are you buying that cost $2000 but can't be sold for $350 three years later? I bought a three-year-old high-end ThinkPad for a friend for $750 recently. Cost twice as much as a new econobox, benchmarks were worse, but it was still a great deal for a far better user experience.
The following article from the New England Journal of Medicine has a good summary of why the Vaccine Injury Compensation Program exists, and why some of its recent decisions, including the award in the Poling case, have been problematic. Basically, since 2005 the policy has been to concede cases where petitioners establish a plausible theory by which their injury could have been caused by the vaccine, rather than requiring proof or even scientific evidence that the vaccine caused said injury.
See also the Wikipedia article on the program, which also discusses the Poling case.
"Too large for a phone" is a matter of opinion. This is exactly the size of phone I've been waiting for. I want as large a screen as possible, without making it impossible to hold it to my ear for my (very occasional) voice calls, or conveniently carry it in a holster or (less often) a pocket.
For me, a phone being tiny is of little value. Give me vast amounts of screen space, a large physical keyboard with hard keys with spacing and some travel distance, and a huge battery that won't run out even if I spend all day using it heavily in areas with poor signal. The Dell Streak isn't what I want, having only the screen space but not the physical keyboard and an unknown battery (and an obsolete OS), but the size? Perfect.
"Not useful for serious business"? Depends on your business. Much of my business is coordinating employees via email and text message, keeping records in spreadsheets and simple text documents, and occasionally consulting and searching through previous emails and web-based resources. A smartphone with a 5" screen, a reasonable array of apps, and a keyboard that lets me do 50wpm, is just fine for this.
Even my T-Mobile Sidekick was adequate for most of my business needs, despite the dubious browser and poor screen, thanks to the ultra-quick app switching and utterly fabulous hard keyboard unmatched by any other device. If Microsoft hadn't bought the platform, stripped it of development resources, and left it to die, I might still be using it.
Sure, this large a phone isn't for everyone. But that's one of the lovely things about an open OS - you have choices in hardware. I'd rather use iPhone OS, it's a far smoother user experience, but where am I going to find an iPhone with a 4-5" screen? or a physical keyboard? or running on a carrier other than AT&T?
If Adobe loves Apple, they have a funny way of showing it. When they ship versions of Flash Player for OS X that are even less efficient and even more buggy than the Windows versions, and publicly acknowledge that making Flash for OS X anything more than barely usable is a low priority because they'd rather work on the Windows and mobile versions, that doesn't sound like love to me.
even a player keeping a perfect count cannot create a significant edge.
Funny how much time they spend scrutinizing players who "cannot create a significant edge", isn't it? You kinda wonder why they even bother barring them. Except, of course, if your hypothesis is completely bogus...
If you gamble in a casino with the belief you can win in the long run, you are an idiot. Winning is an anomaly, it has to be for the business to work.
Smart players are an anomaly. Thus the business can work even if some of the games are beatable.
the casino operators are not stupid.
You haven't spent much time in casinos, have you? They're among the most inertia-driven bureaucracies you'll ever see.
Option 1: Your analysis is incomplete and inaccurate.
Option 2: Countless media portrayals and first-hand accounts of card counters making money are all wrong. Media reports of expensive anti-counting technical measures are part of a casino conspiracy to make people believe blackjack is beatable. Books and conferences on blackjack game protection are hoaxes. People who've been barred from multiple properties based on information in the Griffin book are making it all up. Lawsuits against casinos whose security guards have roughed up card counters are actually filed by insiders as part of this elaborate theater they're putting on to increase public interest in blackjack.
You're pretty smart. Can't be #1. Must be #2!
The article says Google is crowdsourcing their data, but if so, where's the input? When I click on "My Location", I just get a message that "Your location could not be determined" - I don't see any followup on "so where are you, so we can add this location/wifi-signal pair to our database".
For what it's worth, Loki gets my home location exactly right, while Google doesn't even venture a guess.