groby_b

I can almost guarantee you that by the time you need a survival assistant, you won't be willing to spend gasoline on generating electricity for your GPUs.

(It's helpful for shorter outages. But "survival assistant", I think not, unless you run a compound)

No. That is definitely impossible. Nobody gets to serve five terabytes.

I mean, so is murdering people in cold blood, that's why ICE doesn't really do that.

My first was a 2CV, so there may be nostalgia goggles. Also, my current is a Wrangler, and, well, suspension is not its winning move :)

No, but very much no-Vichy french.

You keep your source tree on a separate file system with version control, one hopes.

So you only snapshot the rest. (And since your source tree is under version control, finding stray garbage there is straightforward unless you checked it in)

No, a moveable couch. One of the most comfortable cars ever. (It was designed to be a vehicle that farmers could use to e.g. transport eggs to the market - hence, soft seating and amazing suspension)

It also opened automatically if you made the mistake of leaving a tunnel at the same time as the truck in the lane next to you.

Clean tear at the front.

Life never wasn't exciting with a 2CV.

Ahem. Having driven a 2CV, that top speed literally only applies to the first revision. (So, yes, technically "the original")

Later versions could do 65mph. 75mph downhill with the wind at your back.

Nice, thank you for clarifying! Looking forward to giving it a try tonight :)

It's meaningless anyway, unless you have a calibration approach the home page doesn't mention. Aligning a phone to within 10 arcseconds of where your scope is pointing is... ambitious :)

It would be easier if you could use an eyepiece adapter. I have no idea why the page claims "The field of view is typically too small for plate solving to work." for that approach - it works just fine with a FOV of at least 0.2 degrees or so, which is much smaller than what most beginner/intermediate scopes have.

And if you do have a scope with a smaller TFOV, I'd argue you're likely not the target audience for the app. (Yes, you can get there cheaply and as a first scope, but it's not the usual route)

Edit: I want to be clear it's not a diss on the app - it's great. Plate solving at that speed is pretty cool. I just wish it'd work at smaller TFOVs :)

None of the developers ever saw one, or they firmly believe focusing on iOS makes the product more 'luxe'

What do you think happens to data center water? (It either evaporates or is recycled)

That page is a lot of ink for very little data. It's also somewhat wrong - no, you can't claim the axis marks and labels aren't data ink at all just because it doesn't directly reflect the measure. They are still data that's extremely relevant to reading the chart. Yes, even if Tufte says otherwise.

Meanwhile, even Tufte's advice was explicitly to grey them down, but not completely remove them.

(And we can debate Tufte's advice - lots of other comments on this page how he had great aesthetic sensibility, but his advice wasn't grounded in reason or actual readability research, and so is limited to the examples he chose)