273
Clock but we saved DB space by just returning the index of the array of DigitNames (lemmy.world)
submitted 1 year ago by to c/programmer_humor@programming.dev
37 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (5 children)

What an acid trip of a site. It updated while I was scrolling and legit thought I was having a flashback.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 year ago (4 children)

    I ran into the same thing - they seem to change (potentially to other outputs from the same model?) when you click on the Question mark and go back.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 1 year ago (3 children)

    Question mark says they are updated every minute, even gives you a prompt.

    Watching for several minutes, none of then was good except Kimi K2. Sure, not every time, but solid third of them was actually working, while the others scored a perfect 0.

    Also, as a Kimi K2 user (because Kagi), I approve. I don't use Kimi K2 for coding, though, because JetBrains doesn't offer that, but I use it in Kagi Assistant.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago (2 children)

    deepseek v3.1 had an (almost) perfect clock once for me.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •