Charlie Loyd @vruba@everything.happens.horse

How different can two reasonable pansharpening algorithms be? Pretty different in pathological cases like planes in flight. Left is from Maxar, right is from Potato (the thing I’ve been tinkering with). Same underlying data, from the Maxar Open Data Program, CC BY-NC.

Comparing it to C, a language where the usual error handling mechanism is “rename some integers to things in all caps that start with the letter E and insert them in-band”, a system that a dead iguana could see the problems with, seems almost unfair.

Rust feels like it’s designed by people who actually care about what they’re doing and have paid full attention, which is the highest praise I can imagine giving software tooling.

If you’d asked me a month ago I would have said I simply do not have fun writing in low-level languages, but I would have secretly thought: The actual problem is C, a bad language that is unpleasant to deal with. Now I feel the same way but am more confident in it.

Wrote a small amount of Rust over the holidays and, oddly, enjoyed it?

An analogy for what people are doing when they treat consumer imaging hardware like it’s perfect when it shows “orbs” or whatever: If you turn the volume way up on recordings made with even very high-quality audio hardware, you hear a hiss, which proves invisible hissing aliens are everywhere.