parshimers

As far as I know, only one is awaiting trial because he was brazen enough to think he wouldn't be arrested, and the rest that are indicted are not within reach of the law.

It's still a slap on the wrist either way. They aren't going out of buisiness any time soon because of this. These companies do things we send average people to jail for, on a regular basis ( https://www.justice.gov/usao-cdca/pr/9-charged-federal-court... ).

Amazing. If you get caught with so much as a non-stock air filter on your car, you can get hauled into criminal court (at least in California). If the car maker actively conspires with ill intent, to cheat the test, all they need to do is "fix" it and promise not to do it again.

"Yeah, Nice."

>Same statement was made about Japan in the 1980s, and look at them now.

What, look at the fact Japanese cars out-sell American ones three decades later (~12% vs ~19.6%)? American car makers were even trying to copy their methods in the 90's (NUMMI & Geo, Ford+Mazda, etc...).

It's a reality. The nickel smelting operation in Norilsk, Russia is so polluting that you can mine the topsoil downwind of the smelter feasibly: http://www.nytimes.com/2007/07/12/world/europe/12norilsk.htm...

"Yeah, well, you know, that's just, like, your opinion, man."

"Oh Amygdala, Oh Amygdala... Have mercy on the poor bastard!"

Porter Ranch and most of the area in the northwest area of the valley is pretty green.

"Oh, yes... Paleblood. Well, you've come to the right place."

It works just fine in Nautilus for me.

The danger of leaving a kid in the car is heat if it's warm outside. That may or may not have been a reasonable concern based on the circumstances.

Oh, that's a much better version! Thank you. I thought I linked to the text-only google cache, but perhaps not.

Quite impressive. You know your blog is good when folks will try to take down a CDN to supress what's on it. He's also had heroin mailed to him in combination with a swatting attempt before: http://webcache.googleusercontent.com/search?q=cache:gEjqPfc...

Funny to see something like this here. I went with my dad on some airplane wreck hunts when I was younger, though none quite as epic as this one. You'd really be surprised how complete some of these plane wrecks are if they are hard to get to. One I recall was a F-104 thunderchief. It was just amazing to me that they didn't try to remove any of this stuff: https://imgur.com/a/5uToG

Ah, very fond memories indeed. See also: XFree86.conf .

That dog closing the door for him with the tug rope!

Raise your hand if you thought this was a post about a new Dwarf Fortress patch....

Actually, yeah. They added them on Foothill Blvd in Tujunga a while back. I seriously have never seen anyone ride a bike in one, and I drive around there at least weekly. Vineland between Lankershim and the 101 is also a good example, but that's a bit denser. The lane is just huge though.

Very true. I also hope all of this finds some sort of equitable way to de-sprawl somewhat. Transit in LA does have such an interesting history of missteps. Can you imagine what things might be like if they never got rid of the red car system?!

I would say the main deterrent to riding a bike in LA is the fact the city is not dense, not the lack of bike lanes. Very few folks can afford to live anywhere close to where they work in LA. I don't know how one would solve that fairly, but, I don't think making bike lanes where they have little use (e.g. where it is a bedroom community) helps.

The new trains and stuff are nice. Some of the other aspects of this "Mobility Plan" are really annoying. The main one I dislike is how some already incredibly busy streets have had a whole lane sliced out for a bike lane. It's usually empty, and not that safe, because of people turning right across it. I get that everyone having a car in LA is not a way to allow greater density, but, it's reality for now and making everyone in that reality suffer isn't a great way to get re-elected. More light rail lines, awesome, making driving a car more miserable than it is, not so much.

I wonder how they found something so small and far out. It's almost like something wanted us to discover it ;)

"Their main immediate abode is a still undiscovered and almost lightless planet at the very edge of our solar system—beyond Neptune, and the ninth in distance from the sun. It is, as we have inferred, the object mystically hinted at as “Yuggoth” in certain ancient and forbidden writings; and it will soon be the scene of a strange focussing of thought upon our world in an effort to facilitate mental rapport. "

20. I tried it earlier, but I just couldn't figure out the interface.

This is just an educated guess, but it could be an issue with the on-disk record formats. A quick look here: https://www.sqlite.org/fileformat2.html shows that variable length types like BLOB and TEXT are denoted by a type code value greater than 12 that is even or odd (respectively). The only wiggle room looks like values 10 and 11, but of course there would have to be some completely separate way of denoting the size.

That's actually super handy. Next time I have to add someone to a shell account, I'll probably just look them up on GitHub first to find their public key instead of asking.

TIL: Tethys might look like a moon, but it's really a shrine to Khorne.

They are very useful in log structured merge tree (LSM) based storage. HBase uses them, for example. The idea is to have a bloom filter as part of each on-disk component, so that one can look at the bloom filter first- and then only bother with searching the actual component, if there is a match in the filter. That way you can reduce the pain of having to potentially search multiple indices on disk.

Docker is really great for developing things IMO. I use it in a few ways actually. One thing I've found it really useful for is isolating build slaves in Jenkins (using the docker-cloud plugin in Jenkins).

I also like to use it to create test deployments for debugging or evaluating things, for example it's a lot easier to run Hadoop in pseudo-distributed mode inside a Docker container with host networking, than it is to fiddle with running it in a VM and either getting NAT or DNS working just right, or installing it locally. With the Docker container, if anything goes awry, it's just so easy to get back to initial state by killing the container and starting again.

As for Vagrant, I like it a lot too, but for different reasons. You can define a set of actions that is a lot closer to installing whatever it is you are developing, instead of baking everything together like you do with Docker, which can be desirable. I have used it in the past for creating virtualized cluster environments for integration testing of distributed systems. I think so far I use the VirtualBox provider, but I'm thinking of re-working some of my past uses of it that don't strictly require a VM to use the Docker provider.

Debugging through the test cases in particular is a good way to decipher/dissect things, at least that I have found. Usually you can find a test case that is only for a specific component that you are interested in, and then the test case should only exercise those pieces, so there is not an overwhelming amount of information all at once.