This is beautiful and I've never thought about this before:
the convention we have in Unix to pass pre-opened stdin/stdout/stderr fds is not just a nice way to tell the program where to read its input from and output its result/logs to; it is exactly how capability passing should work in a capability-based system. This also is another reason why accepting an -o option (for "output file") is a bad idea.
We wrote an open letter (in French) to protest against France's renewal of their Elsevier subscription for 4 more years:
#CategoryTheory to formally model "stuff, structure and properties".
> given groupoids c,d and a functor u:c->d, the objects of c can
be thought of via the forgetful functor u as objects of d with
an extra _property_ iff u is full and faithful, as objects of d
with extra _structure_ iff u is faithful, and as objects of d
with extra _stuff_ regardless. -- James Dolan
The "Selfie" attack on TLS 1.3 explained, and why formal verification efforts didn't catch it:
93% of paint splatters are valid Perl programs
https://git-send-email.io/ is live! 🎉
This is an interactive tutorial which will teach you how to use git send-email to contribute to open source projects using git's built-in email tools.
Depuis que je sais que « force » en latin, ça donne « vim » à l’accusatif, je me dis que « J’utilise vim » ressemble beaucoup à une phrase de Star Wars parlée en #latin. 🤔
I learned about golden #testing from here
Initially I thought "what's the point" but I eventually saw the light. Keep the raw data separate from test scripts, so when it changes intentionally you can easily --accept it instead of messing around pasting strings into your source code.
Now with golden tests for error messages, which also act as free samples to show what they look like: