You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be a viable option to introduce alternative time formatting approach?
It is long time already I only code Go, everything is good, but time.Format proves again and again it was not really good decision for folks like me: I still remember how to do formatting with strftime despite years I didn't touch it, yet I need to go to time.RFC3339 to remember what numbers I need to apply after just a couple of months when I was not using it.
This may be different for others of course, but I may be not alone.
So, may be to introduce time.Strftime?
Another alternative could be YYYY-MM-DD hh:mm:ss where, unlike in Java, everything longer than an hour + zone format uses capitals and everything else uses lowercase. IMO it is even easier to memorize than strftime format.
The text was updated successfully, but these errors were encountered:
Hi!
Would it be a viable option to introduce alternative time formatting approach?
It is long time already I only code Go, everything is good, but
time.Format
proves again and again it was not really good decision for folks like me: I still remember how to do formatting with strftime despite years I didn't touch it, yet I need to go totime.RFC3339
to remember what numbers I need to apply after just a couple of months when I was not using it.This may be different for others of course, but I may be not alone.
So, may be to introduce
time.Strftime
?Another alternative could be
YYYY-MM-DD hh:mm:ss
where, unlike in Java, everything longer than an hour + zone format uses capitals and everything else uses lowercase. IMO it is even easier to memorize than strftime format.The text was updated successfully, but these errors were encountered: