I’ve often (only half) joked that there are billions of people alive who have never died, so why should we consider it inevitable?
Well, someone has actually worked out the ratio. Hey, 7% odds of survival beats zero.
[Update a couple minutes later]
Speaking of which Peter Thiel seems to finally be getting serious about longevity, not only funding non-profit research, but actually investing in companies pursuing it.
…has a new CEO. I know they’ve been looking for one for a while. While I’ve never discussed it with him, I suspect Jeff is relieved; he’s probably been trying to replace himself for a long time. It will allow him to focus more on the company’s technical issues, while retaining overall strategic control as board chairman.
The engine of the one under which she’s about to be thrown seems to be warming up.
The Dems are like jackals. When they see a weak member of the herd, they go in for the attack.
BTW, when you see them attack people like Trey Gowdy for a “partisan” attack, it’s almost always projection.
I’m not sure, he’s sort of subtle, but my neighbor Kurt Schlichter doesn’t seem to think that Her Hillaryness is going to be president.
“I’ll assume he’s alive until I see the corpse.” One other possibility is that there’s been a putsch, perhaps over the assassination, and he’s under arrest, but they haven’t figured out who’s in charge yet to make an announcement. But usually such things are resolved much more quickly.
Just did an up
gradedate in Fedora. Looks like the new systemd has broken Chrome. Anyone have any ideas? Nothing about it at the site that I saw, at least based on a Google search. This is sort of a PITA, because Chrome is the only way I can access Tweetdeck, which I need for my multiple Twitter accounts.
[Update a while later]
This is the error message I get when I run from command line: “Failed to create /home/*****/.pki/nssdb directory.”
[Update late afternoon]
I realize the title may be a little cryptic. Every time Chrome fails to open, I get a message that systemd had a problem. Before the update, no problem, after the update, borked.
OK, partially solved problem. If I disable SELinux, I can fire it up. Then I can re-enable. Here’s the errors when I run it:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[7630:7630:0315/162457:ERROR:sandbox_linux.cc(325)] InitializeSandbox() called with multiple threads in process gpu-process
[7571:8329:0315/162710:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates
[7571:7605:0315/162710:ERROR:mcs_client.cc(644)] Failed to log in to GCM, resetting connection.
And there about about ten instances of chrome sandbox process running. Not sure what this means, but at least I can use it for now, until I figure out what’s going on. Unfortunately, I lost all recent history.
A few weeks before its annual conference, a space policy update.
…going dark as a $15 wage looms.
Morons. I find it particularly amusing that they are so precise in what they think the right number is, with Obama’s imbecilic $10.10. It’s like when Roosevelt arbitrarily raised the price of gold twenty-one cents “because it was three times seven.”