The '50 extra packages' one is wild. The author of those packages has racked up a fuckload of downloads. What a waste of total bandwidth and disk space everywhere. I wonder if it's for clout.
Cursed Knowledge
21–30 of 165 posts
Re: Cursed Knowledge
#221 - https://github.com/savely-krasovsky/immich/commit/aeb5368602...
Re: Cursed Knowledge
#23Earlier quoted context omitted.
in what world could mm/dd/yyyy not be cursed!? that makes no sense whatsoever.
It's the US short form, matching the word-month order we always use for regular dates: "August 7, 2025". Note the slashes are important, we don't use dots or dashes with this order. That's what GP was getting at.
Re: Cursed Knowledge
#24Is this true? I couldn’t find another source discussing it. That would be insane behavior for a package manager.
Re: Cursed Knowledge
#25> npm scripts make a http call to the npm registry each time they run, which means they are a terrible way to execute a health check. Is this true? I couldn’t find another source discussing it. That would be insane behavior for a package manager.
Re: Cursed Knowledge
#26> Some phones will silently strip GPS data from images when apps without location permission try to access them. That's no curse, it's a protection hex!
Re: Cursed Knowledge
#27- macOS data forks, xattrs, and Spotlight (md) indexing every single removable volume by default adds tons of hidden files and junk to files on said removable volumes. Solution: mdutil -X /Volumes/path/to/vol
- Everything with opt-out telemetry: go, yarn, meilisearch, homebrew, vcpkg, dotnet, Windows, VS Code, Claude Code, macOS, Docker, Splunk, OpenShift, Firefox, Chrome, flutter, and zillions of other corporate abominations
Re: Cursed Knowledge
#28> Some phones will silently strip GPS data from images when apps without location permission try to access them. That's no curse, it's a protection hex!
Re: Cursed Knowledge
#29Earlier quoted context omitted.
It's the US short form, matching the word-month order we always use for regular dates: "August 7, 2025". Note the slashes are important, we don't use dots or dashes with this order. That's what GP was getting at.
And it makes absolutely no sense. I've lived with it all my life (I'm an American!) and it has never made any sense to me.
But, I think the American-style formatting is logical for everyday use. When you're discussing a date, and you're not a historian, the most common reason is that you're making plans with someone else or talking about an upcoming event. That means most dates you discuss on a daily basis will be in the next 12 months. So starting with the month says approximately when in the next year you're talking about, giving the day next says when in that month, and then tacking on the year confirms the common case that you mean the next occurrence of it.
When's Thanksgiving? November (what part of the year?) 27 (toward the end of that November), 2025 (this year).
It's like answering how many minutes are in a day: 1 thousand, 4 hundred, and 40. You could say 40, 400, and 1000, which is still correct, but everyone's going to look at you weirdly. Answer "2025 (yeah, obviously), the 27th (of this month?) of November (why didn't you start with that?)" is also correct, but it sounds odd.
So 11/27/2025 starts with the most useful information and works its way to the least, for the most common ways people discuss dates with others. I get it. It makes since.
But I'll still use ISO8601.
Re: Cursed Knowledge
#30The '50 extra packages' one is wild. The author of those packages has racked up a fuckload of downloads. What a waste of total bandwidth and disk space everywhere. I wonder if it's for clout.
The author is almost certainly ljharb.