Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cursed Knowledge

immich.app

Post reply on HN
Print view View original

51–60 of 165 posts

Re: Cursed Knowledge

#51

Post by Fwirt »

accrual wrote: post #19
armchairhacker wrote: post #15

Earlier quoted context omitted.

dd/mm/yyyy is most common worldwide (particularly Europe, India, Australia) followed by yyyy/mm/dd (particularly China, Japan, South Korea). https://wikipedia.org/wiki/Date_and_time_representation_by_c... IMO the best format is yyyy/mm/dd because it’s unambiguous (EDIT: almost) everywhere.

I like CCYY-MM-DD because it's also a valid file name on most systems, and using "CCYY" (century + year) instead of "YYYY" feels fancy.

Except this could get confusing because the year 1976 (for example) is actually in the 20th century.

Re: Cursed Knowledge

#52

Post by titanomachy »

bikeshaving wrote: post #21
treve wrote: post #2

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.

The maintainer who this piece of “cursed knowledge” is referencing is a member of TC39, and has fought and died on many hills in many popular JavaScript projects, consistently providing some of the worst takes on JavaScript and software development imaginable. For this specific polyfill controversy, some people alleged a pecuniary motivation, I think maybe related to GitHub sponsors or Tidelift, but I never verified…

This is Wimp Lo! We trained him wrong on purpose, as a joke.

Long time since I thought of that movie.

Re: Cursed Knowledge

#53

Post by [deleted] »

titanomachy wrote: post #52
bikeshaving wrote: post #21

Earlier quoted context omitted.

The maintainer who this piece of “cursed knowledge” is referencing is a member of TC39, and has fought and died on many hills in many popular JavaScript projects, consistently providing some of the worst takes on JavaScript and software development imaginable. For this specific polyfill controversy, some people alleged a pecuniary motivation, I think maybe related to GitHub sponsors or Tidelift, but I never verified…

This is Wimp Lo! We trained him wrong on purpose, as a joke. Long time since I thought of that movie.

[deleted]

Re: Cursed Knowledge

#54

Post by chrismorgan »

Izkata wrote: post #17
dmd wrote: post #14

Earlier 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.

> It's the US short form, matching the word-month order we always use for regular dates: "August 7, 2025".

Counterexample: US Independence Day is called the “Fourth of July”.

I would agree that, for dates with named months, the US mostly writes “August 8, 2025” and says “August eighth, 2025” (or sometimes “August eight, 2025”, I think?), and other countries mostly write “8 August 2025” and say “the eighth of August, 2025”; but neither is absolute.

Re: Cursed Knowledge

#55

Post by jddj »

bikeshaving wrote: post #21
treve wrote: post #2

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.

The maintainer who this piece of “cursed knowledge” is referencing is a member of TC39, and has fought and died on many hills in many popular JavaScript projects, consistently providing some of the worst takes on JavaScript and software development imaginable. For this specific polyfill controversy, some people alleged a pecuniary motivation, I think maybe related to GitHub sponsors or Tidelift, but I never verified…

Looking forward to this Jia Tan sequel in a few years' time.

Re: Cursed Knowledge

#56

Post by a96 »

godelski wrote: post #33

Looks like they're missing one. I'm pretty sure the discussion goes further back[0,1] but this one has been on going for years and seems to be the main one[2] 05/26/23(?) Datetimes in EXIF metadata are cursed [0] https://github.com/immich-app/immich/discussions/2581 [1] https://github.com/immich-app/immich/issues/6623 [2] https://github.com/immich-app/immich/discussions/12292

Datetimes in general have have a tendency to be cursed. Even when they work, something adjacent is going to blow up sooner or later. Especially if it relies on timezones or DST being in the value.

Re: Cursed Knowledge

#57

Post by a96 »

LeoPanthera wrote: post #12

"Some phones will silently strip GPS data from images when apps without location permission try to access them." Uh... good?

Kind of. But that means any file that goes through that mechanism may be silently modified. Which is evil.

Re: Cursed Knowledge

#58

Post by a96 »

LoganDark wrote: post #37
fastball wrote: post #18

Earlier quoted context omitted.

Not only is YYYY/MM/DD unambiguous, but it also sorts correctly by date when you perform a naive alphabetical sort.

I believe YYYY-MM-DD is even less ambiguous than YYYY/MM/DD.

Correct. Slashes mean it's a yank date and going to be backwards. Dashes hint that it's going to be (close to) ISO standard.

Re: Cursed Knowledge

#60

Post by a96 »

hollerith wrote: post #43
dmd wrote: post #23

Earlier quoted context omitted.

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.

Can you explain why on a traffic light, red means stop and green means go? Why not the other way around?

Red is an aggravating colour psychologically. It's pretty universally used as a warning. Red lights in cars also mean "not ready to drive". Brake lights are also red for similar reason. "Seeing red."
Post reply on HN