• Geoff J (unregistered)

    frist!

  • Dlareg (unregistered)

    Actually the earth is cooling, the amount of days with > 10000F water temperature seems to decrease over time.

  • (nodebb)

    File times: it was copied from somewhere else, and the last-opened was preserved. Doesn't explain the other two timestamps, though.

  • (nodebb) in reply to Dlareg

    Actually, only about 9000 degF, approximately 5000 degC / 5273 Kelvin. Which is pretty warm for water to still be actual molecules. Well, steam, at that temperature, of course, or maybe supercritical fluid.

  • davis (unregistered)

    eh, that Azure portal screen corruption is just how IE processes die. Microsoft doesn't seem to be much interested in fixing it. Kill the highest memory/CPU IE process and the tab will reload fine.

  • Bert (unregistered)

    File times: Different computers with differently-set clocks. Alternatively see man touch.

  • MacFrog (unregistered)

    TRWTF is that there are 0.000000000000031 points missing (1001 - 4.409691629955947 * 227). Either that, or non-integer votings were allowed and someone was almost but just not completely satisfied with their headphones.

  • (nodebb)

    It's over 9000 degF!

  • Bert (unregistered) in reply to MacFrog

    That would be a rounding issue.

  • ChrisEvansForBakeOff (unregistered)

    CSV files often make you wish you'd never been born, but that's not quite the same thing.

  • Carl Witthoft (google) in reply to MacFrog

    your rounding is crappier than mine -- I got 1.00100000000000010000e+03 total points.

  • Carl Witthoft (google) in reply to Steve_The_Cynic

    This time-stamp Charlie Foxtrot happens with any Windows(any version))OS where files have been copied from here to there. Apparently fixing stupid bugs is and always has been low on Microsoft's To-Do list.

  • (nodebb) in reply to Steve_The_Cynic

    File times: it was copied from somewhere else, and the last-opened was preserved. Doesn't explain the other two timestamps, though.

    My guess is it’s because of the way the OS XmacOS API saves files: first it saves your document as a temp file in some hidden directory, then it removes the existing file, and finally moves the temp file to the location of the now-deleted one. I have a feeling some of the metadata belonging to the temp file stuck with it somehow.

  • TimothyB (unregistered) in reply to Carl Witthoft

    Created/Modified/Last Opened is an Apple OS thing, not Windows. Windows would be Created/Modified/Accessed.

    Aren't you bashing the wrong OS here?

  • (nodebb) in reply to TimothyB

    Sure, in this particular instance it may not be showing a Windows bug, but I don't think that means Windows doesn't have the same problem.

  • TimothyB (unregistered)

    It also doesn't mean there is a problem in Windows.

    So one by one:

    Modified - the last time the contents got changed. This is the timestamp I typically look at. If I make a copy of the file, it's useful to have the Modified time of the file be the same as the original.

    Created - the time stamp if when this file object was created. When I make a copy of the file, this time stamp is the time of making the copy. It seems strange at first, but makes sense to me. Perhaps only useful for checking up on people who say "but I put it there for you yesterday".

    Accessed - this one gets complex on linux and Windows, and people will disable it to improve performance. Here's a bit about the Windows side: https://blogs.msdn.microsoft.com/oldnewthing/20111010-00/?p=9433/

    So what's the file-time problem in Windows? (I suppose you could bring up the backward compatibility to FAT file-times.)

  • Donald T. (unregistered)

    Alternatively see man touch.

    That's not what I do and that's not what my friend Bill does either.

    Oh wait. Alternatively? Yeah, I support equal rights for alternatives. Or at least I do today, not sure about yesterday or tomorrow.

  • Norman Diamond (unregistered)

    In the St. Paul district it wouldn't take much warming to make the water temperature in the Mississippi River a NaN. Maybe sensors overheated, baking in direct sunlight.

  • (nodebb)

    Those significant digits are important. You never know when some ignorant customer will walk away because the rating is below exactly 4.409691 stars.

  • (nodebb) in reply to CoyneTheDup

    Those significant digits are important.

    They wouldn’t be significant otherwise.

  • O(log n) (unregistered)

    8192 deg F?

  • SomeoneElse (unregistered) in reply to Steve_The_Cynic

    Yeah, files dates can get iffy. Windows considers checking file attributes in Explorer opening for this so unless you use another application to check it's always going to be the current date.

  • SomeoneElse (unregistered) in reply to Steve_The_Cynic

    Yeah, files dates can get iffy. Windows considers checking file attributes in Explorer opening for this so unless you use another application to check it's always going to be the current date.

Leave a comment on “Let's Do the Timestamp Again!”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article