J'ai remarqué quelque chose d'anormal sur mon appareil : l'affichage indique l'année 1980. Cela est particulièrement étrange, car à cette époque, le curseur que nous utilisons couramment aujourd'hui n'avait même pas encore été développé.
16 Comments
Laisser un commentaire
You must be logged in to post a comment.
It’s a null date, but you knew that as a developer, right?
That makes sense now. I wasn’t aware Cursor used a null or epoch timestamp for its build. Thank you.
The file’s modification time has been set to a date that doesn’t match when it was actually changed. This isn’t the Unix epoch timestamp of 1970-01-01, but rather 1980-01-01—ten years later. I’m curious how that occurred.
If you copied it from a FAT-formatted USB stick, that might explain it. FAT uses 1980 as its default timestamp reference.
That must be the explanation.
It might be a broken file. When copying, the file’s data reflects the current date, so if you copy it again later, it will be overwritten. Some file copy applications skip files if the date and size are unchanged.
Good point. I rechecked, and it appears intentional based on how Cursor bundles the app, not a corrupted copy.
That’s the epoch used in the FAT filesystem.