98
submitted 4 months ago by sudoer777@lemmy.ml to c/slop@hexbear.net
you are viewing a single comment's thread
view the rest of the comments
[-] FunkyStuff@hexbear.net 5 points 4 months ago

Admittedly time is always hard, no matter the language.

But a language that doesn't yell at you when comparing different time stamps that may not semantically refer to times in different time zones is a bad language. Python's datetime might be a bit better if you have pylance enabled in your IDE to yell at you, I'm not sure if it would catch this error. Rust's std::time has the decency to not support hardcoding its Instant type, so you have to use external crates that probably force you to specify time zone.

[-] footfaults@lemmygrad.ml 2 points 4 months ago* (last edited 4 months ago)

Python's datetime stuff is quite bad. They really fumbled it and I have to deal with naive vs timezone aware datetime objects. Very annoying. Django at least has warnings when you accidentally use naive objects.

this post was submitted on 30 Sep 2025
98 points (100.0% liked)

Slop.

793 readers
551 users here now

For posting all the anonymous reactionary bullshit that you can't post anywhere else.

Rule 1: All posts must include links to the subject matter, and no identifying information should be redacted.

Rule 2: If your source is a reactionary website, please use archive.is instead of linking directly.

Rule 3: No sectarianism.

Rule 4: TERF/SWERFs Not Welcome

Rule 5: No bigotry of any kind, including ironic bigotry.

Rule 6: Do not post fellow hexbears.

Rule 7: Do not individually target federated instances' admins or moderators.

founded 1 year ago
MODERATORS