there's been quite a bit of research on the cognitive/health benefits of multilingualism, but I think the framing tends to be backwards. multilingualism isn't a bonus, but the default (historically, anthropologically, biologically). our species developed multilingual, and still is everywhere not too damaged by colonial steamrollers. monolingualism is a v recent development, an emergent artifact of a capitalist+racist society.
so we should be talking about the cognitive damage of monolingualism.
[ANNOUNCE] WireGuard Merged Into OpenBSD
git clone DomingosNegros
git checkout git_in_the_night
git add taller_0x08
git commit -m "taller de git!!"
git blame taller_0x08
Más info aquí
Cuando -> Domingo 14 de junio 19:30 (UTC+2)
También hay un pad en el que la gente está preguntando cosas!
And just as a reminder: you don't have to change all the things at once, step-by-step incremental change compounds and goes a long way.
It's also fine to make mistakes and correct them, see this recent-enough example:
This is a topic I've been thinking about for a long time, and what poked me to start changing this default was this:
Apparently some people find that controversial; I call it better, more readable and understandable code and documentation.
And this is not crazy talk, things like the amazingly good Knot DNS server struggle to explain this in their documentation:
If you replace "master" with "primary" and "slave" with "secondary", suddenly the fact that this authority is relative to each zone becomes much easier to explain (and understand).
allow/deny list is simple, direct, descriptive.
[main|primary]/secondary is simple, direct, descriptive; and is more dynamic.
It's easy to imagine things that are "primary" in certain contexts and "secondary" in others, while "master/slave" has a hint of... immutability to it.
Turns out that using non-historically loaded language is actually easier to understand than the current mainstream.
White/black list? Awkard, not obvious if you don't have "white: OK, black: KO" internalised.
Master/[slave|servant]? Awkward, not obvious if you aren't used to absolute, totalitarian and static power dynamics.
Today I was thanked privately for creating and maintaining a #FreeBSD port.
This literally never happened in any other project I was involved in, and I am taking it as a sign of a healthy community.
Sooo.... iocage + vnet works super nicely on #FreeBSD. Somehow hadn't gotten around to testing, I guess the big warning about it being unstable on iocage's docs had something to do with me putting that off.
@fnux willkommen, bienvenue, welcome ;-)
Regarding the whole antifa situation in the US, this is worth remembering…
It's also not just a US thing, I've heard very similar argumentations in the EU.
@mwlucas For best results, wear a face mask with a SQL injection attack printed on it.
Good, realistic take on FreeBSD on laptops.
This mirrors my own experience pretty well:
"Is FreeBSD ready for the desktop? Yes and no. Yes, in that I have a very nice FreeBSD laptop where everything works the way I want. But no, in that it took me two months worth of fiddling with this in my spare time to fix some of the "glitches" which arose"
Also, you have to be pretty careful with your choice of hardware.
chaos.social – a Fediverse instance for & by the Chaos community