News for hackers. Stuff that matters.
Re:Please put units in names by justsomehnguy on Monday March 21, 2022 @03:15AM (#30751150)
Who would even think to check if the system is counting from 1970/01/01 you’re not using their products?
Re:Please put units in names by eyelidlessness on Monday March 21, 2022 @01:19PM (#30756914)
If they’re using ISO format I don’t really care what they’re counting from. But I care if some ISO dates are preserved exactly and some are rounded to another value… especially when that rounding is non-obvious. It took me months to even identify the pattern clearly enough to find an explanation. Up to that point we just had an arbitrary allowance that the value might vary by some unknown amount, and looked for the closest one.
Re:Please put units in names by onlyrealcuzzo on Monday March 21, 2022 @09:13AM (#30753722)
This is an established standard.

It's really not any stranger than starting dates at 1 CE, or array indexes starting at 0.

Re:Please put units in names by justsomehnguy on Monday March 21, 2022 @09:33AM (#30753911)
> This is an established standard.

Established doesn't mean it is understandable without documentation. Anyone who is not familiar with it doesn't know why it starts in 1970 and counts seconds. You need to actually open the documentation to know about that, and it's name (be it unix time, epoch, epoch time or whatever) doesn't help in understanding what it is and what unit it is using.

Re:Please put units in names by hannasanarion on Monday March 21, 2022 @10:25AM (#30754489)
The metric system is also not understandable without documentation, byt you don't need to explain it every time because every living person should have gotten that documentation drilled into them at age ten.

UNIX time is an easy international standard, everybody with computer experience knows what it is and how to work with it.

Re:Please put units in names by justsomehnguy on Monday March 21, 2022 @11:28AM (#30755184)
> everybody with computer experience knows what it is and how to work with it.

Thanks for the laugh.

The only ones who needs to know about unixtime is:

developers when they do something which takes it/produces it

*nix sysadmins

Everyone else with "computer experience" could live all their life without the need to know what unixtime is.

Re:Please put units in names by hannasanarion on Monday March 21, 2022 @11:53AM (#30755512)
Yeah, that's what I meant. People who program or do sysadmin, ie anybody who will ever need to call a sleep function, should know what a unixtime is.
Re:Please put units in names by justsomehnguy on Tuesday March 22, 2022 @03:57AM (#30763646)
> anybody who will ever need to call a sleep function

Bullshit.

I never needed to know what unixtime is when I wrote anything with sleep().

All I needed to know is how long in seconds I want the execution to pause for, never ever I needed to manually calculate something from/to unixtime, even when working with datetimes types.

Re:Please put units in names by hannasanarion on Wednesday March 23, 2022 @12:30AM (#30774968)
No, but as a person who has had a need for sleep() before, you are also the type of person who could be expected to know what unix time is.

Nobody is saying that the two things need to be connected, the point is that it can be name dropped in a type definition, and you would know what it means.

Re:Please put units in names by jodrellblank on Monday March 21, 2022 @03:17PM (#30758476)
https://devblogs.microsoft.com/oldnewthing/20090306-00/?p=18...

Windows uses the Gregorian Calendar as its epoch.