297 private links
Yet another programming language
Dans un second temps, la même expérience a été reproduite en utilisant cette fois le point médian. Les résultats obtenus indiquent que le déséquilibre de temps de traitement entre le masculin et le féminin était alors totalement éliminé : la présence explicite des marques masculine et féminine force le cerveau à considérer les deux alternatives.
Cette étude éclaire à quel point le cerveau est profondément affecté par le biais de genre dans le langage : il tend à présupposer le masculin même face à des phrases n'employant pas le masculin générique.
La stratégie de re-féminisation qui fait apparaître les formes masculines et féminines des mots (par exemple, « Françaises, Français ») apparaît donc la plus efficace pour susciter des représentations mentales équilibrées.
A simple option can be enabled to connect a WordPress site to Activity pub.
As UI evolves, I think we will come one day with a UI library that can be customized entirely (hello white label design system).
Being able to test features on it should also be possible. It don't understand how all accessibility criteria can be tested though.
Des infos, de la veille, des données et des réflexions sur le numérique et les limites planétaires.
Il y a des posts sur la consommation d'eau, les matières premières et composants électroniques, le stockage et l'hébergement, ...
En dehors de la newsletter, un site plus complet est apparu: https://limitesnumeriques.fr
Build minimal BitTorrent, HTTP server, grep, Redis, Docker, Git, SQLite (and more will be added). The guides are not exclusive to rust, and they support manu languages instead.
... oui oui c'est exact
A list of what to do after reading the rust book
Une site web accumulant les archives de la newsletter "Limites numériques". Chaque publication a un effet.
Un flux RSS est aussi disponible.
A qualitative guide that goes through references, blob to commits, to branches, merge and rebase, cherry-pick, tags, fetch and pulling, remotes and the toolkit: fsck, bisect, reflog and stash.
Free speech is a joke on Twitter/X. Another example.
Critics of Git, if someone had to improve from its weaknesses.
sha1 was a bad choice back then. The moral here is "treat your identifiers as opaque strings" along with "sometimes a sha1: prefix doesn't hurt anyone"
Email and names in every commits:
I guess when you read lkml, the notion of spam isn't too worrying, but putting names and emails into every commit means any time someone changes name or email, they might as well be a whole different person to the repo.
Sure enough, when you store names in the files, you have to rewrite history when someone changes email address, but in another world, you'd use a UUID and a file called .gitauthors that maps one to the other
There are two different mechanisms for almost every feature.
git forces you to make a choice. use merge and get a noisy, but representative history. use rebases and lose some of the work, but the log is a lot easier to navigate.
we could also have a version of git log that didn't make merges look like shit, but that's another problem altogether.
the unix philosophy is about building toolkits, not applications
in other words: have you ever accidentally committed inside a rebase? or accidentally committed a conflict? tough shit, fucko.
git commands are named after implementation, not use, and there's absolutely no excuse for it
flat files kind of suck if your state gets corrupted.
git is made from papercuts
there's bits where you can't check in an empty directory, or how you can set files to ignore but not files to include.
La fenêtre d'Overton, aussi connue comme la fenêtre de discours, est une allégorie qui situe l'ensemble des idées, opinions ou pratiques considérées comme plus ou moins acceptables dans l'opinion publique d'une société.
Il s'agit de glisser vers l'impensable au populaire avec ces différents status d'acceptation:
- Impensable
- Radical
- Acceptable
- Raisonnable
- Populaire
Set options for an input field. Here some demo :)
UTF-8 is an encoding. Encoding is how we store code points [of Unicode] in memory.
The simplest possible encoding for Unicode is UTF-32. It simply stores code points as 32-bit integers.
UTF-8 is a variable-length encoding. A code point might be encoded as a sequence of one to four bytes. One or more code points can build a character.
Side effects of UTF-8:
- You CAN’T determine the length of the string by counting bytes.
- You CAN’T randomly jump into the middle of the string and start reading.
- You CAN’T get a substring by cutting at arbitrary byte offsets. You might cut off part of the character.
If you want a character comparison, you should be iterating on "extended grapheme clusters", or graphemes. A grapheme is a minimally distinctive writing unit in the context of a particular writing system. ö is one grapheme. é is one too. And 각.
Is Unicode hard only because of emojis?
No, for example, ö (German) is a single character, but multiple code points (U+006F U+0308).What is 🤦🏼♂️ length?
It depends of the encoding used: 5 for Python, 7 for JavaScript / Java / C#, and 17 in Rust. That’s what extended grapheme clusters are all about what humans perceive as a single character. And in this case, 🤦🏼♂️ is undoubtedly a single character.Before comparing strings or searching for a substring, normalize!
Because code points can be in different order for a grapheme. Also we want to be able to search for 2 in 𝕏².
Unicode is locale-dependent, because two grapheme with the same code points can look different in two languages.
So no, you can’t convert string to lowercase without knowing what language that string is written in. [...] I live in the US/UK, should I even care?
Yes.
What are surrogate pairs?
Unicode decided to allocate some of these 65,536 characters to encode higher code points, essentially converting fixed-width UCS-2 into variable-width UTF-16.
A surrogate pair is two UTF-16 units used to encode a single Unicode code point. For example, D83D DCA9 (two 16-bit units) encodes one code point, U+1F4A9.
The top 6 bits in surrogate pairs are used for the mask, leaving 2×10 free bits to spare: 1101 10?? ???? ???? to 1101 11?? ???? ????'
Is UTF-16 still alive?
Yes. The only downside of UTF-16 is that everything else is UTF-8, so it requires conversion every time a string is read from the network or from disks.