Editing Talk:2867: DateTime
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
::::It's saying that "months have either 28, 29, 30, or 31 days" is a falsehood. The first one that comes to mind is the [https://www.timeanddate.com/calendar/julian-gregorian-switch.html switch from the Julian calendar to the Gregorian calendar]: "In North America, for example, the month of September 1752 had only 19 days, as the day count went straight from September 2 to September 14". [[Special:Contributions/172.70.43.108|172.70.43.108]] 21:03, 14 December 2023 (UTC) | ::::It's saying that "months have either 28, 29, 30, or 31 days" is a falsehood. The first one that comes to mind is the [https://www.timeanddate.com/calendar/julian-gregorian-switch.html switch from the Julian calendar to the Gregorian calendar]: "In North America, for example, the month of September 1752 had only 19 days, as the day count went straight from September 2 to September 14". [[Special:Contributions/172.70.43.108|172.70.43.108]] 21:03, 14 December 2023 (UTC) | ||
:::: (Ninjaed, with an actual example! But retrying reply anyway as it had other details.) But how many days had <insert your choice of month(s) during which a given system changed from Julian to Gregorian>? I think possibly, without looking up when each and every transition occured, below 20 days is possible. (As in the ''n''<sup>th</sup> of one month to the ''n''<sup>th</sup> of the next is less than 20 days, for the right month and a number of ''n''s. For other ''n''s, you can only actually count from the month before to the month ''after'' (two full calendar months), the daycount for that being below the typical bimonthly stretch of 59, 60, 61 or 62 days (under more standard conditions)... [[Special:Contributions/172.70.90.48|172.70.90.48]] 21:07, 14 December 2023 (UTC) | :::: (Ninjaed, with an actual example! But retrying reply anyway as it had other details.) But how many days had <insert your choice of month(s) during which a given system changed from Julian to Gregorian>? I think possibly, without looking up when each and every transition occured, below 20 days is possible. (As in the ''n''<sup>th</sup> of one month to the ''n''<sup>th</sup> of the next is less than 20 days, for the right month and a number of ''n''s. For other ''n''s, you can only actually count from the month before to the month ''after'' (two full calendar months), the daycount for that being below the typical bimonthly stretch of 59, 60, 61 or 62 days (under more standard conditions)... [[Special:Contributions/172.70.90.48|172.70.90.48]] 21:07, 14 December 2023 (UTC) | ||
− | |||
Related insanity on Computerphile with Tom Scott: https://m.youtube.com/watch?v=-5wpm-gesOY [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 03:54, 14 December 2023 (UTC) | Related insanity on Computerphile with Tom Scott: https://m.youtube.com/watch?v=-5wpm-gesOY [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 03:54, 14 December 2023 (UTC) | ||
Line 14: | Line 13: | ||
Even with just Special Relativity, the question doesn't really make sense, because the answer will depend on the inertial reference frame. "Impossible to know and a sin to ask" is not a bad way to describe questions about non-invariants. [[Special:Contributions/162.158.154.189|162.158.154.189]] 08:09, 14 December 2023 (UTC) | Even with just Special Relativity, the question doesn't really make sense, because the answer will depend on the inertial reference frame. "Impossible to know and a sin to ask" is not a bad way to describe questions about non-invariants. [[Special:Contributions/162.158.154.189|162.158.154.189]] 08:09, 14 December 2023 (UTC) | ||
:Is it even ''possible'' for two observers to agree on the answer and be sure that it's correct for both of them? [[User:BunsenH|BunsenH]] ([[User talk:BunsenH|talk]]) 16:53, 14 December 2023 (UTC) | :Is it even ''possible'' for two observers to agree on the answer and be sure that it's correct for both of them? [[User:BunsenH|BunsenH]] ([[User talk:BunsenH|talk]]) 16:53, 14 December 2023 (UTC) | ||
− | |||
I can see Randall's point, so for your average everyday programming I'd say "please use a library function instead of trying to do it yourself, or you'll end up like the guy in the lower frame..." --[[User:IByte|IByte]] ([[User talk:IByte|talk]]) 11:02, 14 December 2023 (UTC) | I can see Randall's point, so for your average everyday programming I'd say "please use a library function instead of trying to do it yourself, or you'll end up like the guy in the lower frame..." --[[User:IByte|IByte]] ([[User talk:IByte|talk]]) 11:02, 14 December 2023 (UTC) | ||
Line 21: | Line 19: | ||
:Ideally, the standard library functions for a language would cover many of the "quirks" without the programmer having to worry about remembering the details. The required inputs for the functions would be sufficient to determine the necessary offsets. But programmers still have to be careful about some of the issues, and not all languages (and their libraries) are sufficient for all situations. When things like relativistic effects have to be taken into account, the usual languages (and their libraries) don't have the needed flexibility/complexity and precision. [[User:BunsenH|BunsenH]] ([[User talk:BunsenH|talk]]) 00:18, 15 December 2023 (UTC) | :Ideally, the standard library functions for a language would cover many of the "quirks" without the programmer having to worry about remembering the details. The required inputs for the functions would be sufficient to determine the necessary offsets. But programmers still have to be careful about some of the issues, and not all languages (and their libraries) are sufficient for all situations. When things like relativistic effects have to be taken into account, the usual languages (and their libraries) don't have the needed flexibility/complexity and precision. [[User:BunsenH|BunsenH]] ([[User talk:BunsenH|talk]]) 00:18, 15 December 2023 (UTC) | ||
::I should clarify, I'm not saying the Python library doesn't have functions for those quirks. I'm just asking: what does Randall mean when he says "DateTime" (two capital letters, no space, as per the comic title)? Is he talking about the Python library? Or something else I didn't find yet?[[Special:Contributions/172.69.134.163|172.69.134.163]] 02:51, 15 December 2023 (UTC) | ::I should clarify, I'm not saying the Python library doesn't have functions for those quirks. I'm just asking: what does Randall mean when he says "DateTime" (two capital letters, no space, as per the comic title)? Is he talking about the Python library? Or something else I didn't find yet?[[Special:Contributions/172.69.134.163|172.69.134.163]] 02:51, 15 December 2023 (UTC) | ||
− | :::Doesn't matter. For one the usage of CamelCase in such cases is pretty much standard regardless of language and besides of that the problems he's talking about/implying are pretty much true for every language. [[User:Elektrizikekswerk|Elektrizikekswerk]] ([[User talk:Elektrizikekswerk|talk]]) 10:58, 15 | + | :::Doesn't matter. For one the usage of CamelCase in such cases is pretty much standard regardless of language and besides of that the problems he's talking about/implying are pretty much true for every (high) language. [[User:Elektrizikekswerk|Elektrizikekswerk]] ([[User talk:Elektrizikekswerk|talk]]) 10:58, 15 December 2023 (UTC) |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |