You can't AC your way out of climate change anyway: they make heat. In sparsely populated areas that might be okay, but in density, you're never far from the hot exhaust of an AC unit; they exacerbate the problem.
Why would the limit of T1 devices matter when there are ones that already can do hotter? Thermodynamics make things harder to remove heat but not sure how they forbid it (you need the hot side to be hotter than outside to pump heat). Might need stages, for example. We can cool things 200K and more below ambient.
> What we're going to do when that tech will cease to cool us?
Move. This is already happening, with water shortages forcing people to move. Climate change will (likely) cause famines and many deaths, but the bigger effect will be mass migration.
I don't remember the details, roughly it was unexpected invocation of move semantic, causing use after free in a loop.
My all-time favourite example is (again, my memory, I may be a bit wrong):
for (int i = 0; i < (size_t)limit; ++i) {
}
at some point limit could potentially become greater than INT_MAX, the compiler decided that i<limit could never be true because that would cause signed int overflow which is UB, so it "optimized" the loop into
The compiler cannot optimize that into `while(true)` because the original code does not encounter undefined behavior when `limit` is small enough to fit into `int`.
What it can do: infer that `limit <= INT_MAX` and use that to optimize the code following after the loop (and in some cases, even the code before the loop).
The comparison to pandoc seems needlessly hostile. Most users get pandoc as a standalone binary (e.g. the Debian package).
Pandoc is a bit on the larger size, but for what it offers (templating, lua filters, built-in templates for all supported markup languages) it is entirely reasonable.
That's fair, but I didn't mean to critisize Pandoc, it was an excellent tool. My point was that for my own use cases, I wanted a much smaller standalone binary for simple conversions. Rudoc is more focused on a narrower scope.
AFAIK it is always backed by a sqlite DB. That way the sync just populates the DB and the completion process doesn't care (or wait for) the central source.
reply