Agent641@lemmy.world to Programmer Humor@programming.dev · 1 个月前Clock but we saved DB space by just returning the index of the array of DigitNameslemmy.worldimagemessage-square38fedilinkarrow-up1296
arrow-up1296imageClock but we saved DB space by just returning the index of the array of DigitNameslemmy.worldAgent641@lemmy.world to Programmer Humor@programming.dev · 1 个月前message-square38fedilink
minus-squaretyler@programming.devlinkfedilinkarrow-up4·1 个月前deepseek v3.1 had an (almost) perfect clock once for me.
minus-squareDerpgon@programming.devlinkfedilinkarrow-up1·1 个月前Did it show the correct time? Did it tick correctly? From my observations, even clocks that looked okay had like wrong second speed, swapped hour and minute, or was rotated altogether.
minus-squaretyler@programming.devlinkfedilinkarrow-up2·1 个月前Yeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.
minus-squaretyler@programming.devlinkfedilinkarrow-up1·1 个月前Yeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.
deepseek v3.1 had an (almost) perfect clock once for me.
Did it show the correct time? Did it tick correctly? From my observations, even clocks that looked okay had like wrong second speed, swapped hour and minute, or was rotated altogether.
Yeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.
Yeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.