Not just a war on Christmas, but an actual war too: this led to a whole bunch of Christmas riots throughout England, including Canterbury's famous "Plum pudding Riots", where rioters ended up sacking the mayor's house and taking over control of the city for weeks. The whole of Kent ended up revolting after the rioters' trial, essentially starting the Second English Civil War.
Putting API contracts aside, the problem is also that people use a package manager as if it was a code snippet manager.
As in, "how do I check if a string starts with a shebang" should result in some code being pasted in your editor, not in a new dependency. There is obviously a complexity threshold where the dependency becomes the better choice, but wherever it is it should be way higher than this.
See the Linux documentation's "How the development process works" [0].
The way a changeset goes from a developer's machine to the root is reasonably similar (it usually gets pulled through a number a intermediate trees, from a development tree to a sub-subsystem tree to a major subsystem tree to Linus's tree), riding the train from the bottom to the top, with an additional time constraint on it (the merge window being open).
The kernel also has a "next" tree that is a snapshot of what the kernel would look like with incoming changes merged right now, surfacing early the exact long-distance coordination issues described in the article. Plus, of course, everything is in the open, so maintainers of different subsystem can then coordinate directly on things that impact both sides, even if the required patches will if possible make their way up separately.
Since mpv 0.34 it even looks for yt-dlp first, and fallback to youtube-dl otherwise. Before that you had to set an option, or just symlink youtube-dl to yt-dlp.
Unicode has both MICRO SIGN (U+00B5) and GREEK SMALL LETTER MU (U+03BC). The former is the one on (most) people's keyboard, and it shouldn't be used to type actual Greek.
There is a new mount syscall in Linux 5.12, see "ID remapping in mounts" [1], that should help with all the permission madness, eventually.
It allows different mounts to expose the same content with different ownership, and in general to map permissions IDs between mounts in any way we like.
systemd-homed wll use that to abstract over the uids and gids of portable home directories, for example.
To be fair, this is more a Rust Syntax Reference Sheet than any kind of cheat-sheet. It basically has everything.
It's useful to quickly lookup the syntax for something you never use, for example. Or to browse and discover things you didn't know were even possible.
That reminds me of the two anti-tanks fortresses disguised as houses as part of the Toblerone line [1]. Those two were the only ones visible from the road by people (i.e. tourists), so they made them a bit less scary.
The Tim Traveller did a wonderful video on those a few months ago [2].
This seems to misrepresent why people bother naming things. It's not like mathematicians are spending their time randomly naming every object/property/structure/... they encounter just for the sake of it.
A "Kähler manifold" exists, as a name, because there is no way to fully describe what it is (and bring forward in the reader all the corresponding context) in two or three words. Using a long sentence (full of things that could themselves be artificial labels, recursively) instead would be a waste of everyone's time.
If one can use a short descriptive name for something, then it's not a name, it's just the thing, and everyone refer to it directly. And when you can't, or when you want to indicate its importance, or you want to neatly package all the relevant context about it, all the mathematical baggage that should come with it in something short, then the pretty obvious thing to do it to abstract it away and stick a label on top.
It doesn't really matter whether they use mathematicians, flower names or characters from The Lord of The Rings, as long as it's unique enough, in context, then it's fine. The names become part of the vocabulary of the field, just as much as supposed "descriptive" names. All those "descriptive" names have to be precisely defined too anyway, because they carry natural-language connotations, assumptions, and so on, that just don't apply.
> Did this used to be open knowledge and scrubbed now?
The [edit: wikipedia] article mentions that he was "director of radio operations of the Psychological Warfare branch in the Office of War Information at Allied Force Headquarters": that's what became PWD/SHAEF [1] towards the end of the war and was merged after the war with the Strategic Services Unit and some other stuff to make the CIA.
> With the deprecation of Adobe Flash Player, there is no longer a need to identify users on 32-bit version of the Firefox browser on 64-bit version operating systems[, ]reducing user agent fingerprinting factors.
Good. User agents already contain too much.
That's actually the first time I've ever seen a browser actively removing stuff from the User Agent.
Not just a war on Christmas, but an actual war too: this led to a whole bunch of Christmas riots throughout England, including Canterbury's famous "Plum pudding Riots", where rioters ended up sacking the mayor's house and taking over control of the city for weeks. The whole of Kent ended up revolting after the rioters' trial, essentially starting the Second English Civil War.