3 ms·
Occasionally, but less often than one could imagine! About a dozen times in my life. Whenever February 29 wasn’t present as an option, the frontend was at faul
by yanateras 3y ago
Occasionally, but less often than one could imagine! About a dozen times in my life.
Whenever February 29 wasn’t present as an option, the frontend was at fault, so I could set the right <input> value in the inspector as a workaround.
Other times February 29 was present as an option, only to be saved as February 28. Never March 1, which I’d say would be more coherent.
- whycome 3y ago> more coherent depends on what you're trying to organize by. maybe 'birth month' is an important signifier.
- yanateras 3y agoHere’s why: * I was N years old on February 28th this year * I will be N+1 years old on March 1st this year Therefore: * I was N-1 years old on February 28th last year * I was N years old on March 1st last year Perhaps the month is February and the non-leap year date is March 1st...
- nyczomg 3y agoIf it makes you feel better.... On February 29, 2008 I was working on a system as a government contractor. Part of it was outsourced to a sub-contractor who decided to write their own date/time library because how hard could that be (which I only learned about later)? For some reason NOTHING would work right that day. Took me longer than I'd care to admit of staring at the logs to realize that some started with March 1 2008.... edit: also happy birthday!
- yanateras 3y agoDefinitely not any more coherent on a leap year! That remark only applied to dates stored without a year, as in “February 29” rather than “February 29, 2008”. Thank you..!