robryk @robryk@qoto.org

@PawelK And this'll end up being one more reason to treat homeless with suspicion :( @freemo

@trevorflowers

Would some simple optics be beneficial in helping create those artifacts? (Or rather, beneficial enough for that to make sense.)

Things that come to mind that might be:
- pixel shape distortion (but that might be easy with a very slight superresolution),
- pixel shape and cross-pixel blending (but that would require one (Fresnel?) lens per pixel, which would probably be very hard to produce~~).

Also, are there ways to replicate the CRT's refresh cycle (both the existence of the flicker and the fact that each pixel is dark for a large fraction of the time)? I guess you could blink the backlight?

@swetland @phooky

@antanicus Where is the quote from?

@Reddebrek Do you know how much of the effect comes from reflecting/scattering the sunlight away and how much from absorbing the sunlight and evaporative cooling? (And am I missing some other important heatsink involved?)

@fluepke What would happen if you clicked any of them?

@duponin Ah, in that case you'll be familiar with large part of Go's concurrency paradigm, and will clearly see the places where it's weird.

Go's typing is.. weird? Large part of it is sort-of duck typing.

@terceranexus6
Can you describe the whole setup? Can you check if e.g. your bashrc doesn't happen to have `set -e`?

@tamtararam

@duponin If this is your first programming language, I'd suggest neither -- both of these languages have some issues that e.g. leave out ability to specify constraints that are useful in reasoning (e.g. constness), so if any of them is your first language you need to figure out that such constraints are useful yourself.

If this is just "what would I want for sysadmin-like purposes", then I'd go with Go if you expect to be doing anything nontrivially concurrent, and would have no opinion otherwise.

@omnipotens Do you expect them to play in sync? If so, have you tested in semi-manually with two devices? I would expect this to either be fiddly, or to require getting the devices to talk to each other for synchronization.

Some part of our "ability" to read things from faces of other humans seems to be projection, while we intuitively think otherwise: https://en.wikipedia.org/wiki/Kuleshov_effect

@WanderingBeekeeper

But when I look at small billiard balls
They aren't like normal billiard balls
They can pass through both slits
Just like light they deblur a bit.

Should I say that light is like balls
Or that balls are like light
And that I don't know balls at all?

@be Are you sure that the rear light doesn't contain one? I wouldn't be surprised if it used one of those terribly small MCUs that cost a fraction of a penny.

@cwebber You might wish to add an exception for being sick, too.

@moonbolt

At least in Polish, it's not "men" but "masculine sapient[^] entities". The "personal masculine nouns" part makes this extremely weird, because e.g. grammatical gender of "human" is male (so if you talk about a group of humans, you always use masculine-personal gender), but grammatical gender of "kid" is neutral (so if you refer to a group of kids, you always use the non-masc-personal gender, regardless of the group's composition).

Aside: Nouns that match some pattern decline differently based on this distinction (e.g. if you think of elves as sapient you'd call them "elfowie" and "elfy" otherwise), which I find to be somewhat endearing (modulo the gender asymmetry), because it embeds some nontrivial information about the speaker's opinions about the world into their speech.

[^] for some value of; it's terribly underspecified and it changed over time (IIUC it used to include at least some animals: "ptakowie niebiescy" was an actually used expression)

@niconiconi Also, don't retry more quickly when you receive an error (or some specific kind of error). If you think of it in these terms it's pretty obvious, but it's something that people sometimes get wrong by omission.

@chjara I remember some software that copied crontab format defining that "?" in a field means "pick a value at random" (so ?/30 in minutes would mean "for two different values of minutes, 30 minutes apart, but with a random offset") and had it implemented by hashing the entry (so that it doesn't need to even store the random value). I can't find now what software was that.

@feld
The result of doing so was a multi-hour outage, probably a few hours of work, and loss of something like an hour or two of comments. If any other component that was shared between both servers had the same issue (e.g. CPU, any part of the motherboard, ...) the result could have been very similar (modulo the data loss). Would you also suggest CPU/motherboard/NIC/... supplier diversity between primary and backup? If not, is there a reason why it's more important for storage (or maybe SSDs in particular)?

@artemis