robryk @robryk@qoto.org

@rq What would you expect the compiler to do in the desired world if it couldn't determine whether the assumption is always held?

@rq What did you mean by blow up? I thought you meant safely crashing. If so, you can add the verification at the beginning of the function itself and crash there.

@rq

Why doesn't checking if it's in the range at the beginning and blowing up if not do what you want?

@rq

There's also the chaotic (and confusing) option: alternate between different ones.

@lauren @m0xEE

The photo is to prevent overeager creation of thumbnails from links in the post. I am also baffled by `ls -l`.

@matthew_d_green BTW you might find https://github.com/google/wuffs interesting.

Hm~ on the off chance it's obvious to someone: I'm trying to use the built-in I2C hardware in STM32Lsomething. I use RIOT-OS's library for interacting with that I2C hardware, and what happens is that as soon as the pins are switched to the alternate function of I2C they get pulled down (afterwards it seems that no I2C operations ever complete, but that's not that weird considering this messed up initial state). Is there something obvious I could be doing wrong, or something I ought to check?

@matthew_d_green

Then we'd have likely picked webp as one of those formats (IIRC it's better than png and git for lossless compression, but please don't trust my imperfect recall).

Alas, many computers are battery-powered now, so lack of optimization for energy usage remains noticeably bad. On the runtime performance side, the will to improve decompression speed grows with increasing available bandwidths (because decompression becomes a larger fraction of the total latency), as long as we continue to compensate for those increases by increasing the amount of data we send in equivalent situations.

@matthew_d_green The whole point of compressing images is that your phone receives fewer bytes. If we didn't care how many bytes it receives we'd do exactly what you said with some format equivalent to PNM.

@LukaszOlejnik The existence of permanently off-limits areas is amusing. (IIRC some part of beam dump infrastructure is like that.)

@freemo @JonKramer @Free_Idealist @pyranose @georgetakei

It doesn't seem to be about boundedness: consider open interval (0,1). There is no leftmost point, and yet the interval is bounded.

@baldengineer Is the script for the video public somewhere? (I'm asking because I vastly prefer reading over watching something that tries to explain stuff to me.)

Mam wrażenie, że bezrefleksyjna powszechność zwrotu "głosowanie za kimś" powoduje podobnie dużo szkód jak "aresztowanie za coś".

Powszechny jest pogląd, że głosowanie polega na wybraniu kandydata, którego najbardziej chcielibyśmy widzieć wybranego. Nawet w przypadku wybierania jednoosobowego organu nie jest to sposób, w który najlepiej możemy realizować nasze preferencje (nawet nie może, bo nie zależy od tego, których z pozostałych kandydatów wolimy bardziej). W przypadku organów wieloosobowych sytuacja jest jeszcze bardziej skomplikowana, bo przestrzeń możliwych preferencji jest większa.

IMO warto myśleć o głosowaniu nie jak o wyrażaniu poparcia dla konkretnego kandydata, ale jak o wyborze, który ma skutki. Jeśli mamy do dyspozycji rozsądnie dobre przewidywania wyników wyborów, możemy poszacować jak każdy możliwy wybór może wpłynąć na wyniki.

Eh, chyba powinienem po prostu napisać taką symulację i ją udostępnić.

@irenes @nazgul

I don't know whether modern fighters are stable with no control inputs (either from pilot or from avionics). If they are, destroyed electronics do not completely preclude stable level flight.

I wonder whether modern fighters purposefully crash themselves after an ejection.

@kh

In some cases it might also be a variant of caring for others where you care for others about as much as you think they care for themselves.

@art4857@101010.pl

Śmieszne jest też to, że plany niebronienia istotnej części kraju nie były rzadkie, chociażby https://de.wikipedia.org/wiki/Limmatlinie (pt. nie bronimy np. połowy Zurychu) i https://de.wikipedia.org/wiki/Schweizer_R%C3%A9duit (pt. prawie nie bronimy całych nizin).

@danderson @mattb

The thing is that time.Time _contains_ time.Location.

@sgf @tubetime

You might find it amusing that Block I Apollo CM (the one that only flew uncrewed on Apollo 4) had mechanical mission and event clocks.

@tubetime Is "autosyn 2" the fine one?