gardarh

Closer to 9 miles (15km). That's plenty (even though it doesn't sound like much), considering what kind of eruption this would be and how the fault lines lie.

To be entirely fair I had the exact same problem with a "knob" interface. The variable resistor in the AC knob broke down putting the AC in the "just blow air as hard as you can, always" mode.

With a fully digital solution it should even be easier to provide workarounds for situations like that (e.g. remote screen on your phone). I'm not a big fan of touchscreens in cars though, but this particular argument doesn't feel strong to me.

Reminds me of the time I decided to always start using braces for if statements. I was figuring out why this line didn't work:

  if(condition)
     doSomething()

And naturally the obvious thing do to was to add a debugging statement:

  if(condition)
    logSomething()
    doSomething()

And if I remember correctly all of a sudden the bug didn't exist anymore for the condition I was reviewing. Took me a while to figure out what was going on. Lesson learned: Just always use braces.

I spent two summers planting for the Icelandic forrest service and I imagine that is more or less how I and my coworkers looked like (well, somewhat less feminine I suppose). You shouldn't extrapolate too much from the newspaper picture.

A few years back I had a short interaction with Kenneth Reitz. I sent an email about some issue in requests and got a reply within a minute telling me that the issue had been fixed in a release published a few hours prior.

Considering how hugely popular requests is I imagine my message was just one of so many he answered on day to day basis and he did all this without really needing to do any of it.

I guess I understand how he and other people in similar situations get tired of it all after a while. For whatever its worth requests is an amazing project and has made my life easier in my personal and professional hacking.

Well if the official stance is that there is no problem then why should they do that?

I think you're forgetting the cookie warning.

Actually, I think the strictness of python3 with regards to bytes/strings is particularly useful for people who speak English as their first language. python3 will force them into writing software that can work with international strings whereas python2 code written by an English speaking person would in many cases just be broken for the international users.

And believe me, as an "international" person, this is profoundly annoying and has trained me in avoiding using the non-ASCII letters of my language which of course "castrates" the written language somewhat (i.e. When people use non-ASCII letters for folder names I think they are just asking for trouble - how normal is that?)

I love how upfront python3 is with the difference between raw bytes and strings. I work a lot with python and in particular I do a lot of work with serializing and deserializing stuff from/to binary blobs. Due to platform issues that I hope will change in the next year or so I can't use python3 currently but I keep all my code compatible with both and all tests should run with python2 and python3. Yes, I am firmly in the python3 camp :)

pycharm inspection definitely helps with keeping code compatible with 2 and 3.

Generally speaking, if you have physical access to device, all bets are off. Which when you think about it is the point of the whole article.

You'd want to separate that complexity from your kernel modules by using some intermediate, e.g. mqueues, named pipes or shared memory.