In a moment of whimsy I briefly considered a date format where digits were sorted alphabetically.
2026-07-02-16-31-52 -> -----00011222235667
Hopefully it will remain a nonsense and never be seen in the wild, unlike the phone number field which I found on a real website which responded to scroll events to increase and decrease the value it contained.
Well that's just totally ambiguous. What you should do instead is treat the date as one long number and present its factors, for instance 2⁴⋅11⋅7649⋅15050023, much more practical.
Just look at your crontab, love.
It is now.
In a moment of whimsy I briefly considered a date format where digits were sorted alphabetically.
2026-07-02-16-31-52 -> -----00011222235667
Hopefully it will remain a nonsense and never be seen in the wild, unlike the phone number field which I found on a real website which responded to scroll events to increase and decrease the value it contained.
Well that's just totally ambiguous. What you should do instead is treat the date as one long number and present its factors, for instance 2⁴⋅11⋅7649⋅15050023, much more practical.
3 replies →
That's not alphabetically, that's asciibetically. The alphabetical (English) sort would be something like ::--51176632222000
How about just sort the numbers from biggest to smallest?
2026-07-02 16:45 becomes
2026-45-16-06-02
Bonus points for using a very confusing separator... Maybe {?
3 replies →
Wait, can this format be transformed back to the "normal" format? If so, then it could be kinda viable for some operations... :thinking_emoji:
5 replies →
Well it's a NUMBER
1 reply →
[dead]